Add TableNameResolver to tempest2

[szabado-faire]

I'm running into a limitation of tempest2 - static table names. This is a limitation that tempest doesn't have, because it allows callers to pass in a DynamoDbMapperConfig that includes either an override or a table name resolver (relevant javadoc)

The AWS v2 client library doesn't support a way of resolving/overriding table names. I think this is because the enhanced client allows you to pass in the table name as a string, removing the need for the v2 client to care about how the name gets resolved. Unfortunately tempest2 uses AWS v1-esque annotations for table names, which prevents callers from leveraging this flexibility.

I figured I'd take a page out of amazon's book and add a TableNameResolver. It seemed like the most flexible way to allow dynamic table names without breaking backwards compatibility.

Why?

We run multiple gradle workers on the same node in order to run tests in parallel. To avoid conflicts across test runs, we prefix dynamo tables and other resources with the test worker number. That's impossible with tempest for obvious reasons, and has led to a high degree of flaky tests on our tempest-based dynamo tables.

Adding a name resolver will let us prefix table names appropriately and avoid flakiness

[kyeotic]

This looks great, thanks for putting it together :D