[Improvement] Enhanced Metrics Monitoring for Exception Error Codes in Gravitino

### What would you like to be improved?

The current Gravitino Prometheus metrics monitoring includes the quantity and distribution of HTTP error codes. However, there is also a set of corresponding exception error codes within Gravitino: (1000-1100). We hope that if this kind of exception error code is also displayed in the metrics monitoring, it will be more beneficial for developers to observe the health of the entire system and to detect potential problems in a timely manner.

### How should we improve?

_No response_

Start by locating the existing Prometheus metrics that report HTTP error-code quantities and distributions, then trace how Gravitino exception error codes in the 1000-1100 range are produced. Done means the corresponding exception error codes are represented in metrics monitoring so developers can observe them alongside HTTP error codes.

Written by the indexing model from the issue text.