Add more ways to identify a receiver category

[atoulme]

Propose to add additional metadata entries for receiver category.

See below for more context.

==============

          > I just want to point out that we have a way to identify components that use checkpointing as part of their metadata.

Makes sense. We can probably introduce more categorization to the receivers, e.g.:

• push model network receivers (return errors in case of failures)
• periodic scraping of external sources (drops are allowed)
• continuous reading of external sources (with checkpointing)

Originally posted by @dmitryax in #5909 (comment)

[github-actions]

Pinging code owners for cmd/mdatagen: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

Pinging code owners:

• cmd/mdatagen: @dmitryax

See Adding Labels via Comments if you do not have permissions to add labels yourself.

[github-actions]

This issue has been closed as inactive because it has been stale for 120 days with no activity.