Sever client networking cryptographic provider initialisation

[SirCipher]

No description provided.

[codecov]

Codecov Report

Attention: Patch coverage is 9.37500% with 29 lines in your changes missing coverage. Please review.

Project coverage is 51.11%. Comparing base (005eda0) to head (ae29730).
Report is 1 commits behind head on main.

❗ Current head ae29730 differs from pull request most recent head 95fcce3

Please upload reports for the commit 95fcce3 to get more accurate results.

Files	Patch %	Lines
client/swimos_client/src/lib.rs	0.00%	15 Missing ⚠️
server/swimos_server_app/src/server/builder/mod.rs	0.00%	7 Missing ⚠️
runtime/swimos_remote/src/tls/mod.rs	0.00%	6 Missing ⚠️
runtime/swimos_remote/src/tls/config/mod.rs	0.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #670      +/-   ##
==========================================
- Coverage   51.23%   51.11%   -0.12%     
==========================================
  Files         342      343       +1     
  Lines       29584    29520      -64     
==========================================
- Hits        15156    15088      -68     
- Misses      14428    14432       +4     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[horned-sphere]

I think it would be better to allow the user to specify the default CryptoProvider rather than adding it to the configuration. As we're providing a library, the Swim server could form part of a larger application where the user is relying on setting the default crypto provider an they want it used everywhere.

We should then either add a builder method to the server, or a feature flag to the crate (probably enabled by default) that will set the CryptoProvider to our choice that can be used by people who don't want to care about it.