Generate logs to validate that FIPS cryptographic module is enabled at runtime for client/server connections, as recommended in step 3 of https://docs.rs/rustls/latest/rustls/manual/_06_fips/index.html

Log examples:

Startup log (no HTTPS needed):

• Linux, FIPS enabled:

INFO Rustls startup default provider: FIPS is enabled for cryptography.

• Linux, FIPS disabled:

WARN Rustls startup default provider: FIPS is disabled for cryptography.

• macOS:

INFO Rustls startup default provider: FIPS is disabled for cryptography (non-Linux build).

HTTPS logs (only if HTTPS is enabled):

• Linux, FIPS enabled:

  INFO Rustls HTTPS server config: FIPS is enabled for connections.
  INFO Rustls HTTPS client config: FIPS is enabled for connections.

• Linux, FIPS disabled:

  WARN Rustls HTTPS server config: FIPS is disabled for connections.
  WARN Rustls HTTPS client config: FIPS is disabled for connections.

• macOS:

  INFO Rustls HTTPS server config: FIPS is disabled for connections (non-Linux build).
  INFO Rustls HTTPS client config: FIPS is disabled for connections (non-Linux build).

Checklist

• Documentation updated
• Changelog updated

Breaking Changes?

Mark if you think the answer is yes for any of these components:

• OpenAPI / REST HTTP API / feldera-types / manager (What is a breaking change?)
• Feldera SQL (Syntax, Semantics)
• feldera-sqllib (incl. dependencies fxp, etc.) (What is a breaking change?)
• Python SDK (What is a breaking change?)
• fda (CLI arguments)
• Adapters (including configuration)
• Storage Format / Checkpoints
• Others (specify)

Describe Incompatible Changes

Add a few sentences describing the incompatible changes if any.