Formalize client application claim service for use with license checkout API

Client application claims like hardware id and process id can be included in license checkout API calls but a formal signature or service definition does not exist. This issue is about design and implementation of such a service.

See license checkout API client claim documentation, start here: https://docs.scale.10duke.com/api/api-license-checkout/index.html#tag/Enforced-Licensing/operation/checkoutLicenses. Also see heartbeat and release API call documentation as well as the equivalent metered licensing documentation.

Design and implementation shall cover:

• A client application claim supplier interface / contract declaring component
• A default implementation of the client application claim supplier interface
• Licensing API client to use the instance of client application claim supplier interface given to it

Minimum test coverage criteria is proposed as:

• correctness of handling and managing client application claims (basic construct, get and set use case)
• API client implementation must be tested to always send all claims that are returned as a not blank character strings by the client application claim supplier
• default client application claim supplier implementation should be tested to always provide a not blank hardware id claim