Ability to read S3 URI while dryRun instead of relying on Http(s)

What problem are you trying to solve?

My organization uses AWS S3 for hosting Maven repositories, which are accessed using s3:// URIs. While Maven resolves dependencies correctly using these URIs, the OpenRewrite framework seems unable to handle them. This prevents us from effectively running OpenRewrite commands like rewrite:dryRun and utilizing its functionality in our projects.

Describe the solution you'd like

ability to access the maven repository using s3 URI.

Have you considered any alternatives or workarounds?

1. I tried using S3 folder URL https://s3.ap-south-1.amazonaws.com/bucketName.maven.repo/release/
2. I tried using rewrite.yml as
   repositories:
   - id: s3.release
   uri: s3://bucketName.maven.repo/release
   - id: s3.snapshot
   uri: s3://bucketName.maven.repo/snapshot

Additional context

[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
[WARNING] Failed to access maven repository s3://bucketName.maven.repo/release due to: Repository s3://bucketName.maven.repo/release is not HTTP(S).
......

Start by tracing how rewrite:dryRun reads the repositories entries in rewrite.yml and where it rejects non-HTTP(S) URIs. Investigate the existing Maven repository access path and the S3 URI behavior described in the warning. Done means an s3:// repository can be accessed during dryRun without relying on an HTTP(S) URI, with coverage for the repository configuration.