Make project files easier to read and understand

[Nirmal4G]

It's hard to read and understand the repo (because of all the redundant files and confusing logic).
The following changes (although not exhaustive) would improve the contribution experience a little bit better.

• Fix corrupted emojis and symbols
• Fix-up white-spaces and new-lines
• Remove un-necessary and duplicate logic
• Rename missed files from previous renames
• Fix Markdown tests with trailing white-spaces

I hope, these changes, along with the upcoming refactoring #3898 would definitely make this repo better for everyone.

[ghost]

Hello Nirmal4G, thank you for opening an issue with us!

I have automatically added a "needs triage" label to help get things started. Our team will analyze and investigate the issue, and escalate it to the relevant team if possible. Other community members may also look into the issue and provide feedback 🙌

[Nirmal4G]

@michael-hawker @Sergio0694

It may seem like I'm changing things too much but is an incremental change (that's probably why it's hard to review since we can't see full picture yet) and part of a larger refactoring that'll make the codebase better for maintenance and contribution.

I could put all of my changes onto a single branch like @azchohfi did with his winui branch but it'll be harder to review. Even with the formatting and clean-up changes in a single PR, it was hard. So, I'll keep mutually exclusive changes in its own branch and PR.

My goal is to improve the quality of the codebase to be on par with the dotnet repos. I can see that there are people for the actual code of the Toolkit project but only one or two on the build/repo side of things. This is my way of helping to fill the gap.