innodb status metrics for mysql reciever

[naman47vyas]

Description:
ENG: 2320
Added support for new Innodb metrics. Used a new parser as a package for parsing these innodb status metrics. The parser package also has a exporter that can export the entries of metrics for the metadata.yaml, so that we don't need to manually make those entries.

Testing::
Added scrapper tests for successful scrapes.

[naman47vyas]

There is a dependency of this PR, innoParser, which is used to parse the metrics and generate the metadata entries. Once a PR for that parser is merged we'll need to change go.mod files to point to the innoParser's main branch.

[tejaskokje-mw]

No fmt.Println. Either use a proper logging library or let caller handle displaying of error.

[naman47vyas]

Sure I'll change the print statements, to proper logging statements.

[naman47vyas]

Now we are returning all the errors, and let scraper handle error.

[tejaskokje-mw]

Again, no fmt.Println

[naman47vyas]

For a few last commits. We have came up with a way to handle errors. The getInnodbStatusStats() method has two types of errors.
1.) Errors that should cause panic. These are the ones where there is an error with the sql client or while creating a parser itself.
2.) Errors that should not cause a panic. These are the one while parsing a particular metric. For instance if a metric named "Innodb_pending_normal_aio_reads" is failing to get recorded then there would be an entry in the "errs" map with a key as same as the metric name. Now we do accumulate and log this metrics but these will not cause panic.

[naman47vyas]

Also the Parser is now merged in the Innoparser repo, so need to change the go.mod to point at the main branch instead of the "adding-parser-WIP" branch.

[github-actions]

This PR was marked stale due to lack of activity. It will be closed in 14 days.

[github-actions]

Closed as inactive. Feel free to reopen if this PR is still being worked on.