Introduce AllocateTableStorage in Storage interface

[HotSushi]

Summary

We introduce a new method in the storage interface as follows:

Storage {
  String allocateTableSpace(...)
}

which returns the tablelocation where table objects will be created.

Implementations of this api should also execute one time operations such as creating buckets, assigning permissions etc.

Please note the comment:
this method should avoid creating TableFormat specific directories (ex: /data, /metadata for Iceberg or _delta_log for DeltaLake),it describes what shouldn't be done as part of this implementation.

Layering with internal implementations

Internal implementations such as LiHdfsStorage will now have flexibiliity to do one-time operations such as table provisioning.

Changes

• New Features
• Tests

For all the boxes checked, please include additional details of the changes made in this pull request.

Testing Done

• Existing tests run ✅
• Gradle build succeeds ✅
• E2E local tests work as well ✅

[HotSushi]

cc: @sumedhsakdeo , @jainlavina , @ctrezzo

[sumedhsakdeo]

code looks good, had one question about skipProvisioning

[ctrezzo]

Thank you for the work!

I left some comments mainly centered around how we encapsulate the table location manipulation logic.

I have scar tissue from the MapReduce code and converting between Paths, URIs, URLs and having that logic scattered everywhere, so sorry in advance if I am focused too much on this.

[ctrezzo]

Looks good to me. Thank you for providing the extra clarifying comments around issue #121 . I think it makes sense that the logic will be contained in BaseStorage once this issue is fixed and the refactor around allocateTableLocation is complete.