Hive types datetime / tinyint(n,m) / smallint(n,m) / int(n,m) / bigint(n,m) / timestamp(n) are not mapped to Doris types

### Describe what's wrong

Hive columns declared with explicit precision/length annotations — e.g. `tinyint(3,0)`, `smallint(5,0)`, `int(10,0)`, `bigint(19,0)`, `timestamp(19)` — and columns of the Hive `datetime` type are returned as `UNSUPPORTED` by `HiveMetaStoreClientHelper.hiveTypeToDorisType`, which makes those columns unreadable through Doris Hive/HMS external catalogs.

### Behavior

- `tinyint(3,0)` → `UNSUPPORTED` (expected `TINYINT`)
- `smallint(5,0)` → `UNSUPPORTED` (expected `SMALLINT`)
- `int(10,0)` → `UNSUPPORTED` (expected `INT`)
- `bigint(19,0)` → `UNSUPPORTED` (expected `BIGINT`)
- `timestamp(19)` → `UNSUPPORTED` (expected `datetimev2`)
- `datetime` → `UNSUPPORTED` (expected `datetimev2`)

### How to reproduce

Create a Hive table with a column of type `int(10,0)` (or any of the above) and query it from a Doris HMS external catalog — the column is reported as unsupported.

### Expected behavior

All of the above Hive types should map to the same Doris type as their plain form (`int`, `bigint`, `tinyint`, `smallint`, `timestamp`), and `datetime` should map to `datetimev2(timeScale)`.

Start with HiveMetaStoreClientHelper.hiveTypeToDorisType and trace how Hive type strings are parsed before the mapping decision. Reproduce the listed annotated integer, timestamp, and datetime cases against an HMS external catalog; done means each returns the corresponding Doris type instead of UNSUPPORTED.

Written by the indexing model from the issue text.