`FloatingPanel` - Conditionally respect device bottom safe area

[des12437]

Found on iPhone 15 Pro on iOS 17, where additional bottom spacing is needed for the Trace button. This issue could be in the floating panel component.

[dfeinzimer]

Ref #209, #210

[mhdostal]

@dfeinzimer is this a regression or an iOS 17 thing?

[dfeinzimer]

is this a regression or an iOS 17 thing?

Regression. We had actually found this last year in #209, fixed it with padding in #210 and then have since regressed it at some point during this release to support forms.

I've found something I've missed in the past. A native sheet will conditionally respect the device's bottom safe area depending on its content. If the content is unmovable (e.g. a button) safe areas are respected. If the content is moveable (e.g. a list) safe areas are ignored and the content flows all the way to the edge of the screen.

Button (Safe Area Respected)	List (Safe Area Ignored)

I've been researching how to do this but I'm not sure we have the API available to do it.

In the meantime some resolution options would be:

• A. Apply padding at the example level for compact environments.
• B. Use a native sheet with background interaction enabled for compact environments (16.4+ only).
• C. Add a parameter to the floating panel to respect/ignore the safe area.
• D. Always respect safe areas in the floating panel (lists won't look great).
• E. Leave as is as known issue.

[dfeinzimer]

Present support for reflection/inspection of SwiftUI Views via the Mirror API seems rudimentary but if expanded in the future it may be useful for this and possibly #551 as well.