fix prestart and pretest (for prettier to work)

Proposed changes

Using prestart we re-generate the env.js file, but the generator does not comply with our prettier rules, so we have to enforce prettier during prestart.

Types of changes

What types of changes does your code introduce to the project: Put an x in the boxes that apply

[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Documentation (improve documentation)
[ ] Continuous Integration (functionality that improve automation or testing)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have read the CONTRIBUTING doc
[x] I have signed the Contributor License Agreement
[x] I have updated the RELEASE NOTES
[x] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)
[ ] Any dependent changes have been merged and published in downstream modules

Further comments

N/A

"Martel Open Source Software Individual Contributor License Agreement"

"Contributing to auth-management-ui"

"auth-management-ui Release Notes"

orchestracities / auth-management-ui