Add ability to parameterize S3 Saves

[kenxu95]

Describe your changes and why you are making these changes

This PR allows a user to parameterize the filepath of an S3 save like this (as shown in the demo):

demo = client.resource("Demo")
s3 = client.resource("test_s3")

table = demo.sql("Select * from hotel_reviews")
dir_name_param = client.create_param("dir_name", default="test")
file_name_param = client.create_param("file_name", default="hotel_reviews")
s3.save(table, "{dir_name}/{file_name}", format="parquet")

client.publish_flow("Test S3 Save", artifacts=[table])

Considerations:

• Using {} interpolation by name is a bit tricky, because it is possible for there to be multiple explicit parameters with the same name. I decided to resolve this by picking the one that was most recently created. Implicit parameters are excluded from this search for obvious reasons.

Limitations and bugs:

• We're currently filtering out these parameterized filepaths from S3 due to time constraints and complexity of the problem. See the slack link in this task: https://linear.app/aqueducthq/issue/ENG-3015/get-list-saved-objects-to-work-with-parameterized-s3-saves
• We should show the resolved filepath in the UI sidesheet: https://linear.app/aqueducthq/issue/ENG-3016/show-the-resolved-names-for-the-spec-fields-on-the-workflow-sidesheet

Related issue number (if any)

ENG-2998

Loom demo (if any)

https://www.loom.com/share/1e616042edd843e9a7845bd619f696c7

Checklist before requesting a review

• I have created a descriptive PR title. The PR title should complete the sentence "This PR...".
• I have performed a self-review of my code.
• I have included a small demo of the changes. For the UI, this would be a screenshot or a Loom video.
• If this is a new feature, I have added unit tests and integration tests.
• I have run the integration tests locally and they are passing.
• I have run the linter script locally (See python3 scripts/run_linters.py -h for usage).
• All features on the UI continue to work correctly.
• Added one of the following CI labels:
  • run_integration_test: Runs integration tests
  • skip_integration_test: Skips integration tests (Should be used when changes are ONLY documentation/UI)

[likawind]

LGTM, since it will soon have customer use case, how hard it is to include an integration test for this?

[likawind]

Just confirming we are not supporting parametrizing a portion of the table name here

[kenxu95]

correct

[kenxu95]

@likawind added a data resource test for it.