Rename SWXMLHash class to XMLHash

[drmohundro]

Related to #242, see comment specifically at #242 (comment).

When creating an XCFramework and the .swiftinterface file is created, there are name conflicts. The expectation is that classes within a module wouldn't share the name with the module. Other OSS libraries like this (e.g. Alamofire) have introduced a new name like AF.

Of course, the hardest part here is naming... in this case, I just went with XMLHash by taking the SW prefix off.

I'm still open to other names for the actual type, though.

Things I want to understand prior to merging:

• How the module name works when using in SPM vs CocoaPods vs Carthage, etc. I want to ensure that the docs are accurate across various dependency distributions.

[codecov]

Codecov Report

Merging #246 (c61b98f) into main (8fe82e1) will not change coverage.
The diff coverage is 97.14%.

@@           Coverage Diff           @@
##             main     #246   +/-   ##
=======================================
  Coverage   74.34%   74.34%           
=======================================
  Files          14       14           
  Lines        1910     1910           
=======================================
  Hits         1420     1420           
  Misses        490      490           

Impacted Files	Coverage Δ
Source/XMLIndexer+XMLIndexerDeserializable.swift	68.94% <ø> (ø)
Tests/SWXMLHashTests/XMLHashConfigTests.swift	63.63% <50.00%> (ø)
Source/XMLHash.swift	83.41% <100.00%> (ø)
...ests/SWXMLHashTests/LazyTypesConversionTests.swift	70.96% <100.00%> (ø)
...ts/SWXMLHashTests/LazyWhiteSpaceParsingTests.swift	75.00% <100.00%> (ø)
Tests/SWXMLHashTests/LazyXMLParsingTests.swift	75.34% <100.00%> (ø)
...SWXMLHashTests/MixedTextWithXMLElementsTests.swift	60.00% <100.00%> (ø)
.../TypeConversionArrayOfNonPrimitiveTypesTests.swift	71.11% <100.00%> (ø)
...SWXMLHashTests/TypeConversionBasicTypesTests.swift	68.50% <100.00%> (ø)
...XMLHashTests/TypeConversionComplexTypesTests.swift	73.52% <100.00%> (ø)
... and 4 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8fe82e1...c61b98f. Read the comment docs.

[fgarciaDev]

In Texas and just getting power and everything back to "normal". Will try this out as soon as I can.

[drmohundro]

@fgarciaDev no worries, totally understand, I've got family in Texas. Stay safe and warm!

[fgarciaDev]

Tested by specifying this branch in my Swift.Package manifest file. Rebuilt my XCFramework and was able to integrate into new projects without the need to manually edit the generated *.swiftinterface files for this library. Appreciate the work!

[drmohundro]

Sounds great! I'd like to at least think about making some possible enhancements as this will be a major version bump. Not at all required, though, but that's my thought process. Sounds like you're good with referring to the branch still, correct? I don't want to cause any blockers for you, though, if I do that.

[fgarciaDev]

yes, pointing to your dev branch is fine for now. appreciate it!

[drmohundro]

Other references to this or similar issues:

• https://bugs.swift.org/browse/SR-898
• https://developer.apple.com/forums/thread/123253
• https://forums.swift.org/t/frameworkname-is-not-a-member-type-of-frameworkname-errors-inside-swiftinterface/28962