Handle RemoteS3Facade dynamic creation in RemoteS3ConnectionController

[mosiac1]

Replace the RemoteS3Facade plugin type with a RemoteS3FacadeFactory that creates RemoteS3Facade instances based on Map<String, String> configs.

Add RemoteS3FacadeManager to create the default RemoteS3Facade from configs in remote-s3-facade.properties.

[Randgalt]

Why a Map? Why not use a real object via Airlift config?

[mosiac1]

I followed the pattern that Trino uses to create plugins.

I can look into changing it to take a Airlift config, but that would essentially just move the code that does

return new Bootstrap(new DefaultRemoteS3Module())
                .doNotInitializeLogging()
                .quiet()
                .setRequiredConfigurationProperties(configs)
                .initialize()
                .getInstance(RemoteS3Facade.class);

from the RemoteS3FacadeFactory impl to the aws-proxy core.

We would also have to update the TrinoAwsProxyServerPlugin to add a function like

    Collection<Module> remoteS3FacacdeModules();

since we would need to use these to create a new Bootstrap context with only RemoteS3Facade modules and instantiate a RemoteS3Facade from the configs returned by RemoteS3ConnectionProvider

This would have the advantage of removing the need for a separate remote-s3-facade.properties config file.

WDYT?

[Randgalt]

I can tell you from experience that the raw HashMap config for connectors is a major headache. Also, Trino plugins/connectors are usually their own context, with their own classloader, etc. We don't want to emulate that.

[Randgalt]

I have serious concerns with starting a new Bootstrap with this library. I feel we're getting into the weeds. Maybe you can explain the need for this offline.

[Randgalt]

Note: log is unused