Refactor: Use static Lazy instance for all sensors

[nickodei]

GitHub Issue (If applicable): closes #19274

PR Type

What kind of change does this PR introduce?

• Refactoring (no functional changes, no api changes)

What is the current behavior?

Most sensor classes use a static instance and track with an boolean if the instance is already created. This caused code duplication and wasn't implemented like the LightSensor.cs implementation.

What is the new behavior?

Use a static Lazy instance for instance creation, which removes the object lock, as well as the boolean. This follows the implementation already in LightSensor.cs.

PR Checklist

Please check if your PR fulfills the following requirements:

• 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)
• Validated PR Screenshots Compare Test Run results.
• Contains NO breaking changes
• Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[unodevops]

🤖 Your Docs stage site is ready! Visit it here: https://unodocsprstaging.z13.web.core.windows.net/pr-19278/index.html

[unodevops]

🤖 Your WebAssembly Sample App stage site is ready! Visit it here: https://unowasmprstaging.z20.web.core.windows.net/pr-19278/index.html

[nickodei]

I tested my changes on the SampleApp for Android with the Android-Emulator mainly by going to the Windows.Devices pages and trying out the sensor events. This all seemed fine to me and changes where registered correctly

[MartinZikmund]

Looks good! 🚀

Thanks for the nice PR @nickodei!