Sort index tags by name so code remains stable between code generations.

[RParkerHp]

• Do only one thing
• Non breaking API changes
• Tested

What did this pull request do?

Sorts tag indexes so code is generated in a stable and consistent manner.

User Case Description

For generated entities that have multiple database indexes associated with them, the ordering of indexes changes on each generation attempt. It therefore means the generated code contains a larger set of changes than is necessary when committed to source control.

[propel-code-bot]

LGTM, ship it! 🚢

Details

Why was this auto-approved?

✅ APPROVED: No issues detected.

[propel-code-bot]

Ensure deterministic ordering of generated index tags

Introduces deterministic ordering for index-driven GORM tags by sorting column indexes by Name() before tag construction. A dedicated helper on *Index slices provides nil-tolerant name-based ordering so generated struct tags remain stable across runs.

Key Changes

• Added helper sortIndexesByName in internal/model/tbl_index.go to sort *Index slices by Name() while handling nil entries
• Invoked sortIndexesByName on c.Indexes within Column.buildGormTag before assembling index-related tag values
• Updated imports in internal/model/tbl_index.go to include sort and strings for the new sorting logic

Affected Areas

• internal/model/tbl_index.go
• internal/model/tbl_column.go

This summary was automatically generated by @propel-code-bot