Support for the ALTER CATALOG statement and the RESUME JOB statement

[ccxxxyy]

for #31491 , for #31501

Changes proposed in this pull request:

---

Before committing this PR, I'm sure that I have checked the following options:

• My code follows the code of conduct of this project.
• I have self-reviewed the commit code.
• I have (or in comment I request) added corresponding labels for the pull request.
• I have passed maven check locally : ./mvnw clean install -B -T1C -Dmaven.javadoc.skip -Dmaven.jacoco.skip -e.
• I have made corresponding changes to the documentation.
• I have added corresponding unit tests for my changes.
• I have updated the Release Notes of the current development version. For more details, see Update Release Note

[terrymanu]

Nice work expanding Doris support: adding ALTER CATALOG/RESUME JOB grammar, AST classes, and parser test cases is on the right track.

Please tighten a few points before merge:

• Assertion coverage: test/it/parser/.../AlterCatalogStatementAssert.java:53,65 only checks rename/comment when actual is present, so missing fields slip through. When the expectation includes rename/comment, first assert isPresent() on the actual optional, then verify the value.
• String handling: DorisDDLStatementVisitor.visitAlterCatalog manually strips quotes for properties/comment. This will mis-handle escaped or nested quotes (e.g., "a", b''c). Use SQLUtils.getExactlyValue(...) (and avoid getChild(0).getText()) to extract keys/values/ comments consistently.
• Keyword compatibility: DorisKeyword.g4 promotes JOB to a keyword. If Doris lexer treats JOB as reserved, fine; if not, this could break identifiers previously named job. Please confirm against Doris’ official grammar and adjust if necessary.

Once these are fixed, the feature should be safe to merge. Keep it up!

[ccxxxyy]

@terrymanu Hi! Hope you could take a look when you have a moment. After reviewing the document, I made the necessary revision promptly.