[Design] Provide mechanism to migrate authentications log to job token allowlist

📝 Summary

This issue focuses on the UX design for providing a mechanism to migrate authentication logs to the job token allowlist.

Users with permission should be able to:

• Populate log entries into the allowlist via a rake task (admin level).
• Add or remove log entries through the UI (project level).
• Handle the 200-entry allowlist limit with automatic common group detection.
• Identify log-populated entries in the allowlist.

🎨 Proposal

Design	Summary
N/A - No new UI elements are introduced.	Instance Level Permissions: Administrators can auto-populate entries at this level by executing a rake task.
	Project Level Introduce action buttons in the UI: Add (auto-populate) Remove (revert) Neither of the action above toggles the allowlist setting. Action buttons and their functionality are available regardless of settings until the feature is removed (#498305). Add an icon to signify projects added from the logs in the allowlist. Permissions: Administrators and Project Owners can perform add and remove actions. 🎨 Detailed design Refer to the design section for details: Add (Populate) Remove (Revert) State (Error Handling and Limit Exceedance)

🔗 Links:

• Figma: Figma project
• Frontend issue: #498125 (closed)
• Backend issue: #478540 (closed)