Data: Documentation: Document undocumented declarations

[aduth]

This pull request seeks to add missing documentation for data module exports:

• plugins
• use
• RegistryConsumer
• RegistryProvider

Implementation notes:

The plugins documentation here could be improved to better reference available options. However, it's not clear how to reference this without adding overhead to future updates to these plugins, which would likely be overlooked. Suggestions welcome.

Testing Instructions:

Verify by rendered output of "Files changed" tab that produced documentation is sensible.

There are only documentation changes. Thus, there is no expected impact on application runtime.

[oandregal]

Prefer the @see tag (see)

[aduth]

Prefer the @see tag (see)

👍 Updated in c10bcab

[oandregal]

I wish we had a better way to auto-document this. Unfortunately, we don't yet.

• One approach could've been using @property tags. Current issue docgen: pull type definitions from @typedef #15186
• Another approach could've been using whatever mechanism we end up implementing to group things together. Current issue: docgen: add support for classes and groups of things #15178

[oandregal]

It looks fine to me, but I defer to other people with more data-foo in case they have any input about the text itself.

[aduth]

Rebased to account for conflicts from #15737, dropping the now-redundant documentation for the registry consumer and provided (previously 1786274).

@nerrad Would you be able to give this a look?

[nerrad]

This is better than what we have currently (certainly better than "undocumented") so I'm in favor of merging this for now and it can be iterated on if needed?