Changed the namespace of ISettingsStorageHelper interface inline with other helpers.

[maroldo26]

Issue link : #403

Closes #403

Changed the namepspace of the interface ISettingsStorageHelper from CommunityToolkit.Helpers to CommunityToolkit.Common.Helpers

PR Checklist

• Created a feature/dev branch in your fork (vs. submitting directly from a commit on main)
• Based off latest main branch of toolkit
• PR doesn't include merge commits (always rebase on top of our main, if needed)
• Tested code with current supported SDKs
• Contains NO breaking changes
• Code follows all style conventions

Existing code which refers ISettingsStorageHelper using old namespace CommunityToolkit.Helpers will break.

[net-foundation-cla]

All CLA requirements met.

[Nirmal4G]

This is a straight forward change. I like it but nonetheless, a huge breaking change; yet not many seem to have used it. So, this might be a good candidate for v8.1 preview to see how the community reacts to the change.

@Sergio0694 Thoughts?

[Sergio0694]

I mean I'd really just like to remove the whole bunch of typed in this namespace entirely, but that's a different topic. The changes here look good to me, though yeah this is a breaking change. I think some libs in Microsoft Graph are using these helpers, so we might have to double check with them first that this won't be too disruptive. @michael-hawker do you know who we'd need to ask, just to double check or at the very least give them a heads up?

[michael-hawker]

There was also the question of here if the Extensions should be removed here as no other extensions use this namespace, eh?

[Nirmal4G]

Should this be moved to Helpers then?

[michael-hawker]

Yeah, this got introduced in the 8.0 update and was really just a copy-paste issue, unfortunate we didn't catch it before hand, so now it's a breaking change. I don't think we're planning a 9.0 any time soon.

Considering the WCT stuff will ship after you do an update, probably good to just push it through. Not sure how best to communicate a breaking change in a minor release though. It's really just a mistake to correct what was intended vs. us actually trying to change behavior, but it's still a contractual break to semantic versioning... 🙁 Probably would have been easier if we did an 8.0.1 soon after release or something we had noticed it right away.

[Nirmal4G]

It's really just a mistake to correct what was intended vs. us actually trying to change behavior...

It probably depends on how many people depend on this directly. I think you can ship a preview to see how many are breaking, even if it's just a few (since, most don't use previews), we can mark this for next major instead!