Add ability to document configuration options in metadata.yaml

[jaydeluca]

Related to #13468

• Adds the ability to document configuration options in the metatdata.yaml file.
• Adds a few more descriptions to a various modules.
• Prints out a small summary of stats related tracking the progress of adding information to metadata files.

Current stats output:

INFO: -----------------------------------
Analysis Summary:
Total Modules: 252
By classification:
	library: 226
	custom: 5
	internal: 21
metadata.yaml contents:
  descriptions: 12 (4.76%)
  configurations: 5 (1.98%)

[laurit]

@trask should we have a framework specific flags for this in all frameworks? I think it was added for a few.

[trask]

yeah, I almost wish we didn't have the "common" variant, to make it harder for users to do the wrong thing (send sensitive data unexpectedly from some other db instrumentation)

[jaydeluca]

would it be worth me opening an issue to replace the common config flags, or at the very least start with this one? I plan on working through module to module to document the various configs, so I can track the common ones I find and replace the usages with framework specific ones as I go, if that's a direction we want to move in.

[trask]

ah, I only dislike this one common flag due to it broadly disabling sensitive data sanitization, the other common flags I like

I'm not sure I dislike it enough though to cause upgrade pain by removing it

[laurit]

Not related to this PR but I guess the peer service handling is a bit inconsistent. I think we are using it only for some of the instrumentations.

[jaydeluca]

do you think it's worth an effort to standardize the approach?

[laurit]

I think we should strive for consistent behavior across instrumentations, but it is one of the many nice to have things.