iOS: Avoid different player plugins from having an implicit order in which they need to be applied

[A1shK]

Is your feature request related to a problem? Please describe.

As a user, I want to load two plugins - PluginXYZ and PluginABC.

Let's say PluginABC, sets an environment object for the player view. Example:

player.hooks?.view.tap(name: "SwiftUI-environment", { view in
            AnyView(
                view
                    .environmentObject(environment)
            )
})

If I register my plugins in the order:

1. PluginXYZ
2. PluginABC

Then its possible that there is a crash when a capability is relying on PluginXYZ but uses the environment object set in PluginABC.

Describe the solution you'd like
Suggestion by @hborawski:

In order to prevent this, we could introduce a SwiftUIPlugin protocol that extends NativePlugin and adds an additional function that builds on top of SwiftUI's transformEnvironment

This would allow plugins like PluginABC to register a handler that sets up the environment, and then SwiftUIPlayer can apply all the environment modifications at once, rather than it being done per plugin, wrapping the view. This would remove this implicit dependency between the two plugins and ensure that all the environment modifications are done wrapping around the root view

Additional context