feat: Implement create/get/delete/list table metadata methods

[mure]

• This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?

• Implements a set of table metadata routes:

  • create
  • get
  • delete
  • list

• Adds a custom serializer for our Pydantic models. This is so we can set certain options like by_alias.

• Switches attribute comments to use docstrings, because some of them wouldn't fit on a single line.

Why should this Pull Request be merged?

We need this functionality.
(This part of the PR template is awkward. I'm never sure what to put other than "because we need it")

What testing has been done?

Added our first functional test 🎉 Feel free to suggest other test cases. I think we'll want at least one that tests an expected error.

[cameronwaterman]

Please change your title to adhere to the Angular style

i.e. "feat: Implement create/get/delete table metadata methods"

It looks like there is also a typo in your existing title 😆

[spanglerco]

Some test ideas:

• Validate we deserialize timestamps correctly by asserting the created_at on the table metadata. We would probably need some kind of threshold for allowed values given that the time on the server may not match the time on the client.
• Retrieve metadata for a valid table ID that doesn't exist (like 000000000000000000000000) and verify we raise the correct exception that includes the error details like the code and args.
• Similarly, we could have an error case for the create and delete APIs.

[mure]

@spanglerco @cameronwaterman I was working off this branch and since the PR is still up, I went ahead and added the list_tables method as well. I'll reset the reviews so y'all can take a look.

New changes: 20f3bbf