Improve collection analyzer

[dr1rrb]

Refactoring (no functional changes, no api changes)

Use generics in more cases in order to avoid boxing of value types, and add a visitor pattern for collection change set.

What is the current behavior?

• We are boxing value types, which is causing issues in comparison and with the nullable annotations.
• Each time we are digging in a collection change set, we are creating multiple NotifyCollectionChangedEventArgs that are throw away right after and we are losing the "Same" (indicates that an item has been kept) as there is no event action for it.

What is the new behavior?

🙃

PR Checklist

• Tested code with current supported SDKs
• Docs have been added/updated which fit documentation template. (for bug fixes / features)
• Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Updated the Release Notes
• Associated with an issue (GitHub or internal)