Need to generate migrations for additional admins

[DenTray]

Description

What needs to be done?

Enhance the existing script that handles admin creation migrations as follows:

• When the user answers 'no' to the question about generating the default admin,

• And also answers "no" to the question about using the default admin for access to Nova/Telescope,

• The script must prompt the user to input additional admin credentials:

  • Email address
  • Password

• After receiving the credentials, the script must generate a new migration(s) file that creates admin user(s) using the provided credentials

• The migration must correctly set the credentials in the database for the new admin(s).

• Ensure the migration follows the existing migration structure and naming conventions.

Expected Outcome

What is the expected result?

• If the user declines default admin generation and default admin usage for Nova/Telescope, the system asks for additional admin credentials.
• A new migration file is created reflecting the additional admin(s) with the user-supplied email and password.
• The migration correctly inserts these admin users into the database when run.
• Input validation prevents invalid email or empty password submission.
• The workflow smoothly integrates with existing migration generation and user setup processes.
• Admin access to Nova/Telescope works with the newly created admin(s).

Verification Scenarios

How can this be tested?

• Run the script and answer "no" to default admin generation.
• Answer "no" to the question about using the default admin for Nova/Telescope.
• Verify that the script prompts for additional admin email and password.
• Provide valid credentials and check a migration file is created that inserts these credentials.
• Confirm the migration file runs without error and creates the admin user in the database.
• Try invalid email or empty password; ensure the script requests valid input again or shows an error.
• Repeat the scenario with no input or cancel; verify proper handling or graceful exit.
• Ensure no default admin migration is generated in this flow.
• Verify no debug information or errors appear during this process.