Add ExtensionType for uuid and map to parquet logical type

[mbrobbel]

Rationale for this change

It would be nice to better support reading and writing the canonical uuid extension type with the arrow and parquet crate i.e. mapping between the arrow extension type and the parquet logical uuid type.

What changes are included in this PR?

This adds an ExtensionType trait, some impls for canonical extension types and CanonicalExtensionTypes enum for canonical extension types.

Are there any user-facing changes?

Users can now annotate their logical types with extension types, and for uuid they are propagated via the arrow writer to map to the parquet uuid logical type.

This needs better tests and better docs, but I'd like to get some feedback on the approach first, because there are many different ways to implement this.

I quickly tested this change with narrow and those uuid fields (in the parquet file) are now picked up as uuid instead of blob by DuckDB.

[kylebarron]

Maybe ExtensionType could be a trait to be externally implementable and not limited to canonical extension types?

[tustvold]

This makes sense to me, and seems like an unobtrusive way to provide better ergonomics for extension types.

That being said I've limited exposure to them so getting some broader perspectives might be valuable, perhaps on the mailing list or something?

[mbrobbel]

I haven't had time to work on this, but I'm planning to pick this up later.

[alamb]

Thanks @mbrobbel -- marking this PR as draft as I think it still has planned but not yet completed work

[aykut-bozkurt]

Thanks for the PR. This seems very useful to support not yet mapped logical types. e.g. json

[mbrobbel]

I updated the PR to define a trait for extension types instead. Ready for another round of feedback.
Edit: just realized I need to change some trait methods to make it work for other extension types.