Request to add functionality to make the default workflow package name unique to prevent collisions when multiple users execute "Publish Now" simultaneously.

Request for Feature Enhancement (RFE) Summary:	Request to add functionality to make the default workflow package name unique to prevent collisions when multiple users execute "Publish Now" simultaneously.
Use-case:	When multiple users manage publication using the "Publish Now" option at the same time, the default workflow package name is duplicated, causing conflicts. This results in publication failures and error messages displayed to users.
Current/Experienced Behavior:	A conflict error occurs because the same workflow package is used in multiple requests when they are made simultaneously. As a result, the following errors occur:  - "Not enough to manage publication" is displayed to users
Improved/Expected Behavior:	The expected improvement is to ensure the default workflow package name is unique, preventing conflict errors. For example, the workflow package name could include the user name and current UNIX time to guarantee uniqueness.
Environment Details (AEM version/service pack, any other specifics if applicable):	Environment: cm-p121411-e1208866 (Production) AEM Release ID: 20133 (Current Latest Lease)
Customer-name/Organization name:	Panasonic (Org Name: panasonicglobal)
Screenshot (if applicable):
Code package (if applicable):

We are currently in the process of migrating from On-Prem to AEM as a Cloud Service, and only about 10–20% of the migration has been completed so far. Encountering this kind of issue at such an early stage raises serious concerns about the stability and feasibility of the full migration. Once the migration is complete, approximately 620 users are expected to use the system. It will be virtually impossible to communicate and enforce the current workaround across such a large user base.