feat: improve error message system.

**Is your feature request related to a problem? Please describe.**

Users can get frustrated when they use `OpenMLDB` in the wrong way. e.g. SQL Syntax errors, unsupported data types, unsupported query on specific running mode. What's worse, the error message can be misleading in some cases which might make users more confused.
So it's very important to improve, _refactor if need,_ the whole error message system in a way to make the error message clear and readable.

**Describe the solution you'd like**

- [ ] support ERROR CODE to identify the error types.
- [ ] error message had better follow some pattern.
- [x] trace msg can be `Exposed` when the DB enable `TRACE`
- [ ] Move hybridse::base::Status to openmldb::base::

**Describe alternatives you've considered**
A clear and concise description of any alternative solutions or features you've considered.

**Additional context**
Add any other context or screenshots about the feature request here.

The issue mentions moving hybridse::base::Status to openmldb::base:: and adding error codes. Look at the current error handling in the codebase, especially around SQL parsing and execution. Start by examining the status classes and error message generation. Determine what patterns to follow and how to expose trace messages when TRACE is enabled.

Written by the indexing model from the issue text.