add UNIQUE or UNQ name to unique indexes in database tables

[jakwinkler]

Description (*)

This table eav_attribute_label has an index defined in db_schema.xml

    <index referenceId="EAV_ATTRIBUTE_LABEL_ATTRIBUTE_ID_STORE_ID" indexType="btree">
        <column name="attribute_id"/>
        <column name="store_id"/>
    </index>

I work on fast database import scripts and tried to add a new unique index in that table:

    <table name="eav_attribute_label">
        <constraint xsi:type="unique" referenceId="EAV_ATTRIBUTE_LABEL_ATTRIBUTE_ID_STORE_ID_UNQ">
            <column name="attribute_id"/>
            <column name="store_id"/>
        </constraint>
    </table>

but unique index name create by Magento 2 is: EAV_ATTRIBUTE_LABEL_ATTRIBUTE_ID_STORE_ID
which is identical to the index defined above and that breaks installation / running db:upgrade schema

Expected behavior (*)

Unique indexes should contain UNQ / UNIQUE in referenceId

Benefits

No conflicts on core tables when new indexes or unique indexes are added.
Ability to create multiple insert scripts.

Additional information

[m2-assistant]

Hi @qsolutions-pl. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

@magento give me 2.4-develop instance - upcoming 2.4.x release

For more details, review the Magento Contributor Assistant documentation.

Add a comment to assign the issue: @magento I am working on this

To learn more about issue processing workflow, refer to the Code Contributions.

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel