WIP: Create implied artifact entries for assets

What does this MR do?

The new release node in gitlab-ci.yaml supports assets which can be added to the release, for example binaries or documentation.

The assets must be defined as an artifact in order to be available to be attached to the release, but in order to simplify the definition of the gitlab-ci.yaml file, assets will be automatically defined as artifacts if not specifically defined.

This MR will take any release:asset nodes which are not defined as artifacts and automatically define them.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Closes #26013 (closed)