feat: client identification headers

[Tymek]

Description

Identification headers consistent with other Unleash SDKs.

This PR adds standardized client identification headers to the feature and metrics calls that the client makes to Unleash. The headers are:

• x-unleash-appname: the name of the application that is using the client. UNLEASH-APPNAME will be deleted in another PR (expand/contract pattern)
• x-unleash-connection-id: an internal unique identifier for the current instance of the client generated by the built-in crypto lib
• x-unleash-sdk: sdk information in the format unleash-client-<language>:<version>

All the headers are intended for the Unleash team. Changes should be implemented in a way that does not change SDK behavior in a significant way.
The main use cases we have are:

• capacity planning by knowing the number of unique connections made to the backend API
• debugging misconfigured SDKs sending more traffic than expected

Fixes issue/1-3275

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Running unit tests locally
• Starting example app and verifying headers sent over the network

Test Configuration:

• Linux, dotnet 6.0.135

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• Any dependent changes have been merged and published in downstream modules

[kwasniew]

I find it weird that we can overwrite unleash-client-mock. I'd expect that it's always unleash-client-dotnet. Also how do we read the real version here?

[daveleek]

@kwasniew don't know if this answers your questions, but the "real" header value is read here from a default implementation in UnleashSettings: https://github.com/Unleash/unleash-client-dotnet/blob/main/src/Unleash/UnleashSettings.cs#L144C31-L144C44

[kwasniew]

I'd fix the original versioning to follow unleash-client-dotnet:semver convention and drop the v prefix

[kwasniew]

one drawback is that there's a lot of existing dotnet SDKs using the v version scheme

[daveleek]

LGTM!