Is your feature request related to a problem or challenge?

Currently, only table API is async, but register_table, deregister_table, table_names, and table_exist can be also async. Also, most of the usage is under async methods, thus there shouldn't be a big issue implementing it.

However, this can be a huge change for the downstream usage, this is why I need some insides before me or someone else implements it.

cc @Dandandan @alamb

Describe the solution you'd like

No response

Describe alternatives you've considered

No response

Additional context

No response