RFC: add signature v4

[AMar4enko]

This is basic implementation for attaching AWS Signature v4 to HttpClientRequest
Usage example is somewhat along these lines:

import { SignatureV4 }  from '@effect-aws/signature-v4/Aws4Fetch.js'
export class ApiClient extends Effect.Service<ApiClient>()(
  `ApiClient`,
  {
    effect: Effect.gen(function* () {
      const { transformClient } = yield* SignatureV4

      return yield* HttpApiClient.make(Api, {
        baseUrl: ApiBaseUrl,
        transformClient,
      })
    }),
  },
) {}

const Sig4 = SignatureV4.Default.pipe(
  Layer.provide(Credentials.layer(awsCreds))
)

const runtime = ManagedRuntime.make(
  Layer.provide(ApiClient),
  Layer.provide(Sig4),
)

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4c34768

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[floydspace]

I suggest using layer for normal options and layerConfig for Config wrapped options
it is quite a pattern within ecosystem
See here or here
also I suggest use Redacted creds end to end so you don't need redactCredentials

[floydspace]

could you clarify why do you need Ref
I feel like using Ref with Layer is a bit off, it makes it impure.
I would rather use the globalValue and 2 functions: withCredentials and setCredentials (hof and setter). see example here, however global value strips Credentials as dependency and requires default value, which suits well if you use shell aws config or sso...