[Subtask] Refactor client side MessagingCatalog to use relative path in NameIdentifier

[shaofengshi]

Describe the subtask

Currently, in the MessagingCatalog.java, the methods like "loadTopic", "createTopic", "updateTopic" all need a NameIdentifier parameter, which needs to be a fully-qualified (metalake.catalog.schema.topic) name. But the "metalake" and "catalog" are not needed, as they already be provided when load the catalog. To make the API clear and easier to use, we will change it to use a relative NameIdentifier object (which is "schema.topic") as the fileset's ID, so that the user doesn't need to provide the metalake and catalog names repeatedly.

Please note, this only affects the client side.

Parent issue

#3626