feat: egress client - ucanto integration

[fforbeck]

Egress Client - UCanto Integration

Context

This PR introduces EgressClient to the application context, enabling capability invocations such as Space.egressRecord for logging egress directly to the UCanto Server (Upload API). With this integration, the previous Accounting Service is now replaced by a method in EgressClient for egress logging.

Key Changes

• Middleware Integration: Added withEgressClient middleware to simplify capability invocations across the application.

• EgressClient Creation: Introduced a create function to instantiate UCantoClient, establishing a secure connection to the UCanto Server based on environment configurations.

• Egress Recording: Refactored EgressClient.record function to use the Space.egressRecord capability, allowing for efficient egress byte tracking in our infrastructure.

• Connection Management: Added a connect function to handle connection setup with the UCanto Server.

• Environment Variables: Updated the environment variables, including service Web DIDs and service URLs.

• Enhanced Context: Added the delegationProofs to the application context, so we can use that information to invoke the egressRecord capabilities. Also added the GatewayIdentity to the application context.

• Accounting Service: There is no Accounting Service anymore. Instead, we use the EgressClient to record the egress event.

• Wrangler: Updated the configs for all environments and the wrangler lib to the latest version.

• Telemetry: Added a feature flag for Open Telemetry - if enabled, the Egress Record call will fail to execute the this.fetch function call. See Fix opentelemetry issue caused in the execution of the invocation project-tracking#176 for more details.

[Peeja]

🫵🥫➡️❗

Looks great! One suggestion:

[travis]

lgtm! agree with Petra but happy to see this ship with or without the change

[Peeja]

Looking good! Suggestions and thoughts below. Looks like this needs some type love and some npm run lint:fixing too.