Add standardized support for device metadata

Nobody has claimed this yet.

@DanielDent [says](https://github.com/liveview-native/liveview-client-swiftui/issues/58#issuecomment-1363602743):

> I'd really like to see standardized support for sending device state information back to the server from the client. Examples I have in mind: app bundle id, version name, version code, device type, language/locale info, OS version, SDK version, install UUID, etc. Likewise with information about permission state (e.g. asked, unasked, granted, denied) for the various permissions an app might need.
>
> Here are some examples of handling of these types of issues with the NativeScript project:
>
> https://github.com/nativescript-community/perms
> https://github.com/EddyVerbruggen/nativescript-appversion
> https://docs.nativescript.org/api-reference/interfaces/idevice
> https://github.com/NativeScript/NativeScript/blob/ee701db13/packages/core/platform/index.d.ts#L121
> Sometimes a new capability or a bugfix requires a new build of the mobile app, and being able to serve different application variations based on the client's version/capabilities/state can be extremely helpful/essential.

These are great ideas, just a bit larger in scope than what I think the original issue asked for. I've moved it here to consider as a general approach to passing device-specific state across any LiveView Native platform 🙂

Start by reviewing the linked NativeScript examples for device metadata and permission state, then examine how LiveView Native platforms currently pass device-specific state. Done means a standardized approach is defined for sending the requested metadata and permission information across platforms.

Written by the indexing model from the issue text.