Store the list of configurations in a separate yaml file

Problem/Motivation

Now the module requires extending the main "my_module.info.yml" file to describe the list of managed configurations like this:

name: My Feature
type: module
description: The description.
package: Features
core_version_requirement: ^10

config_devel:
  - core.base_field_override.node.article.promote
  - core.entity_form_display.node.article.default
  - core.entity_view_display.node.article.default
  - core.entity_view_display.node.article.teaser
  - field.field.node.article.body
  - node.type.article

That is convenient, because we do not need to create and manage a separate file, but this file describes the general info about the module, and this pretty technical information here looks unclear and not very relevant, especially with the _devel suffix in the key name, especially when the module is not deployed on production, but the strings are still there.

Proposed resolution

Probably it'll be more convenient to manage the list of managed configurations in a separate file like my_module.config-relations.yml?

Additional benefit is that the separate file can be easily excluded from deploying to production and from the module released packages (using gitattributes or any other approach).

What do you think about this idea?

If you still want to keep it inside the "my_module.info.yml", maybe consider at least renaming the section from the "config_devel" so something more relevant like "config_relations"? Because the "devel" word looks very technical and unclear for this section.