Regression: Deal with profile dependency

[dogversioning]

Currently, we are using the github action mcblair/configure-aws-profile-action@v0.1.1, which extends the action provided in https://github.com/aws-actions/configure-aws-credentials , as that just loads vars into env vars, and pyathena as we use it today is looking for a specific profile to start from. This has a couple bad side effects:

• The AWS API being used by the extension is going into maintenance mode. The main project has uprevved their API, but there is no indication when (or if) this extension will be updated
• It has a much smaller user base generally, so there's no snowball effects for bug management

We can do one of two things:

• Wait, and hope that this is resolved (though there's an issue about profiles that is three years old on the main project, so we're waiting on how responsive the extension is basically)
• Change the way that we are invoking pyathena, to explicitly pass an S3 path if there is no profile present.

[dogversioning]

waiting it out proved successful - addressed via #203