feat(catalog): Implement MemoryCatalog's table update/ commit path

[DerGut]

➡️ Moved to #1405

Which issue does this PR close?

Relates to #700

This is a first attempt at implementing the commit path for the MemoryCatalog. Happy about any feedback!

What changes are included in this PR?

This PR implements the MemoryCatalog::update_table method. It also adds a MetadataLocation struct to avoid some re-validations of the location format.
I'm very open to removing the MetadataLocation or moving it's addition to a separate PR.

Are these changes tested?

So far, I've included unit tests to verify

• whether a table update that was committed via the MemoryCatalog can be observed in the updated table
• that in the case of two competing updates, the later commit fails if it has conflicting requirements
• that an update fails if the table isn't known to the catalog
• parsing logic of the MetadataLocation

[jonathanc-n]

Thanks for this pr! I do not think we should move forward with this yet before our transaction API is finished. This is a nice start though and can probably be added later and tested alongside the rest of the transaction functionality.

[jonathanc-n]

What do you think? @liurenjie1024 @Fokko

[DerGut]

Works for me, happy to iterate on it later if needed 👍

Is there a ticket for pending transaction API improvements? I couldn't find one.

[jonathanc-n]

#700 This holds most of the improvements for updates, deletes, etc. You can possibly look into the different pull requests that are contributing to this.

[DerGut]

Closed for now. I can recreate the PR once we're there! and recreated in #1405 because I had to rebase onto a new branch 🙈