A bit of code improvement

[Tcharl]

• Some code quality.
• One fix for fakeKeytool option
• Review of the angular generator to only keep methods used in .ejs in generator.ts (also, removal of totally unused methods)

First try to follow #27294

---

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[Tcharl]

Is it considered as correct? I'm a bit reluctant to continue this PR to improve the remaining files (passing over each generator with the same improvments)

[mshima]

My idea is to drop lib/jhipster/index.js.
Choice value usage will be at the generator it's declared.
It can be replaced with something like springBootCommand.configs.authenticationType.choices.jwt.value.

Choices is an array, we should support object.

[Tcharl]

My idea is to drop lib/jhipster/index.js. Choice value usage will be at the generator it's declared. It can be replaced with something like springBootCommand.configs.authenticationType.choices.jwt.value.

Choices is an array, we should support object.

Can we simplify? application.authenticationType ?
The reasoning behind is: if generator-angular/type.d.ts#AngularApplication need something coming from server it should extends SpringBootServerApplication and being taken as a generic default class AngularGenerator extends BaseApplicationGenerator<AngularApplication, AngularEntity>. Does it makes sense?