refactor!: remove export_metrics feature and related configuration/docs

[kumarUjjawal]

I hereby agree to the terms of the GreptimeDB CLA.

Refer to a related PR or issue link (optional)

This PR is related to the issue #6907

What's changed and what's your intention?

As discussed in the issue #6907 the proposal was to Eliminate the export_metrics functionality and related documentation (including the standalone page) and remove the information_schema.runtime_metrics table. I have hunt down all the refrences and removed as per my knowledge.

PR Checklist

Please convert it to a draft if some of the following conditions are not met.

• I have written the necessary rustdoc comments.
• I have added the necessary unit tests and integration tests.
• This PR requires documentation updates.
• API changes are backward compatible.
• Schema or data changes are backward compatible.

[WenyXu]

Hi @kumarUjjawal There are some conflicts

[kumarUjjawal]

Hi @kumarUjjawal There are some conflicts

I will resolve those soon.

[kumarUjjawal]

@WenyXu can you approve the workflow?

[WenyXu]

@WenyXu can you approve the workflow?

Hi @kumarUjjawal, some CI checks have failed. Please follow the CI output for details. For Clippy and rustfmt issues, you can run make clippy and make fmt locally to reproduce them.

[kumarUjjawal]

@WenyXu can you approve the workflow?

Hi @kumarUjjawal, some CI checks have failed. Please follow the CI output for details. For Clippy and rustfmt issues, you can run make clippy and make fmt locally to reproduce them.

Definitely, I will fix those.

[kumarUjjawal]

@WenyXu There are mentions of export_metrics in the config also the server crate contains the export_metrics.rs and the self contained tests, should I remove those as well.

[WenyXu]

@WenyXu There are mentions of export_metrics in the config also the server crate contains the export_metrics.rs and the self contained tests, should I remove those as well.

Yes

[evenyag]

Hi, please fix the CI checks and sign your commits.

[kumarUjjawal]

Hi, I found three variants of SNAFU error that are defined but never used anywhere, that's why one of the checks was failing, what is your preferences for that, should I remove those?

[kumarUjjawal]

The thee failing tests doesn't seem to come from my changes, Can you check?
./tests/cases/distributed/common/view/create
./tests/cases/distributed/common/system/information_schema
./tests/cases/distributed/common/show/show_databases_tables

[evenyag]

Hi, I found three variants of SNAFU error that are defined but never used anywhere, that's why one of the checks was failing, what is your preferences for that, should I remove those?

Sure, it's fine to remove them.

The thee failing tests doesn't seem to come from my changes, Can you check?
./tests/cases/distributed/common/view/create
./tests/cases/distributed/common/system/information_schema
./tests/cases/distributed/common/show/show_databases_tables

They are related to your changes. You should update the sqlness result because you have removed a table from the database.
https://docs.greptime.com/contributor-guide/tests/sqlness-test/

[kumarUjjawal]

Hi, I found three variants of SNAFU error that are defined but never used anywhere, that's why one of the checks was failing, what is your preferences for that, should I remove those?

Sure, it's fine to remove them.

The thee failing tests doesn't seem to come from my changes, Can you check?
./tests/cases/distributed/common/view/create
./tests/cases/distributed/common/system/information_schema
./tests/cases/distributed/common/show/show_databases_tables

They are related to your changes. You should update the sqlness result because you have removed a table from the database. https://docs.greptime.com/contributor-guide/tests/sqlness-test/

Oh! Thanks for the docs.