Disallow the usage of invalid object names in HMS

[findinpath]

Description

Older version of HMS are more permissive in terms of names allowed for schemas/tables. Disallow directly in Trino object names that may eventually cause inaccuracies in the location of the schema/table saved in HMS.

Additional context and related issues

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

[hashhar]

what happens to reads on existing "invalid" names?

[findinpath]

what happens to reads on existing "invalid" names?

The existing object names, regardless whether they are valid or not valid (e.g. : "foo/bar" name) will be passed further to HMS as they are.
The current PR avoids filling potentially problematic object names in HMS which would lead to inconsistencies in the path of the schema / table.

[findepi]

is ci / test (plugin/trino-hive) failure related?

[findinpath]

is ci / test (plugin/trino-hive) failure related?

TestHive3OnDataLake>BaseTestHiveOnDataLake.testCreateTableInvalidName:1675 
Expecting throwable message:
  "Invalid object name: '.'"
to contain:
  "Invalid table name"
but did not.

I think the failure is caused by the fact that this code depends on #17787 changes. Rebased on master.