fclVersion field does not differentiate between languages/libraries

Problem

The fclVersion field passed to providers does not specify which FCL library is sending the request (e.g. fcl-js or fcl-swift). This has the potential to cause confusion for consuming services.

Related: does it make sense to eventually define a global FCL version (i.e. a protocol version) that is shared across all language implementations?

Acceptance Criteria

The service should be able to determine both the library and version from the version field.

Context

This came up in a feature request to add the version field to fcl-swift: https://github.com/Outblock/fcl-swift/issues/4

[chasefleming]

appMetadata doesn’t exist yet. Just a proposed name. client works though too. I do think the option of keeping them separate as configurable vs not-configurable. And the point about thinking a value may be overridable if not separated is a good one. Do we think leaving the fclVersion at the root for now is fine then? Can drop it in 1.0.0 maybe.

And looks like @psiemens and @orodio both like the github url which is more unique of an identifier than a string so works for me too then.

[orodio]

oh i thought appMetadata already exists, client is more than fine thin fine then