[Setup] Add previews to samples

[CalebRas]

Description

This PR adds a preview to the top level view for each sample. Samples that used navigation related components, such as a toolbar, had to be wrapped in a NavigationView to work correctly. Some samples also required some small changes for their preview to compile. Those special cases can be found in the second commit of this PR.

Note: With how on-demand resource are set up in this project, they do not work with previews and cause them to crash. As a result, The samples that use on-demand resource were not given a preview.

List of Omitted Samples (as of creation)

1. Add custom dynamic entity data source
2. Add feature layers
3. Add raster from file
4. Animate 3D graphic
5. Animate images with image overlay
6. Augment reality to show tabletop scene
7. Change camera controller
8. Display dimensions
9. Display map from mobile map package
10. Display scene from mobile scene package
11. Find route in mobile map package
12. Find route in transport network
13. Geocode offline
14. Identify raster cell
15. Show device location with NMEA data sources
16. Show mobile map package expiration date
17. Show viewshed from geoelement in scene
18. Style features with custom dictionary
19. Style symbols from mobile style file

Linked Issue(s)

• swift/issues/4845

How To Test

• Verify the preview in the top level view of each sample works as expected.
• Verify the samples that were additionally modified work as expected.

[yo1995]

Because the branch was accidentally merged into main branch, we need to merge the changes into v.next as well.

• I don't think it is a big problem to have them on main for now as we eventually will have these changes on main some time in the next release, so there is no need to rollback these changes.
• I'll create another PR to cherry pick the most recent 2 commits from main to v.next, if people agree.
• Another way would be restore the Caleb/Update-AddPreviews branch and open another PR against v.next. This would mess up the commit history a bit, but won't be a huge problem? 🤔
• I'll add you to review that PR shortly.
  

thoughts? @dfeinzimer and @rolson

[dfeinzimer]

thoughts?

Maybe it would be cleanest to revert and restore/reopen the PR against v.next?