SPM Prep – Rewrite RemoteBlogSettings encoding and decoding in Swift

[mokagio]

Description

The Objective-C BlogServiceRemoteREST object references the Swift types RemoteBlog and RemoteBlogSettings.

This Objective-C to Swift dependency is incompatible with the separation we require for the SPM setup.

The first step to address this is to move the custom encoding and decoding logic implemented within BlogServiceRemoteREST to Swift.

I did this by first writing tests for the existing implementation and then moving it to Swift using those tests as a guideline.

Testing Details

See new tests in CI.

---

• Please check here if your pull request includes additional test coverage. — N.A.
• I have considered if this change warrants release notes and have added them to the appropriate section in the CHANGELOG.md if necessary. — N.A.

[dangermattic]

	1 Warning
⚠️	This PR is larger than 300 lines of changes. Please consider splitting it into smaller PRs for easier and faster reviews.

Generated by 🚫 Danger

[crazytonyli]

Maybe I worry too much, but do you think we should use number(forKey:) to parse all properties instead of just these keys, because that's what the original Objective-C uses?.

We happen to know these weird cases, simply because we have one test json file for it. There is no indication in the original Objective-C code that these keys need special treatment. And, may be there are other keys needs a special "string" to "number" parsing, which is not detected by that one single test json file?

[crazytonyli]

Also, the string(forKey:) parsing in the original Objective-C code can parse a number to a string, which we don't do here. So, maybe we should use string(forKey:) and number(forKey:) instead of type casting?