Migrate naming series of HD Ticket from auto-increment to custom naming series

[RitvikSardana]

Currently, HD Ticket uses auto-increment integers as document names (e.g., 1, 2, 3). This makes ticket IDs non-descriptive and harder to reference in external communications.

This issue tracks migrating the naming to a human-readable custom naming series such as HD-TKT-.YYYY.-.##### (e.g., HD-TKT-2026-00001).

ToDo

• Update in HD Ticket DocType from autoincrement to a naming series
• Ensure all references to ticket.name handle string names correctly (no parseInt assumptions)

[dankgarlic1]

@RitvikSardana I would like to work on this

[dankgarlic1]

@RitvikSardana Before I finalize the data migration patch for the legacy tickets, could you clarify a few product decisions so we avoid any future ID collisions?

• Preserving Legacy IDs: Should we preserve the existing integer IDs in the new string format (e.g., ticket 90 becomes HD-TKT-2024-00090), or is a clean sequential rename starting from 00001 for all legacy tickets acceptable?

[dankgarlic1]

@RitvikSardana please finalize this, so that I can start the work on backfill patch, rest I have fixed