Split UAA SecurityConfiguration in a distinct template

[murdos]

And move security related templates in a dedicated template directory

---

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

• All continuous integration tests are green
• Tests are added where necessary
• jhipster-online was 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 (bellow reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[murdos]

This one was redundant with

generator-jhipster/generators/server/files.js

Line 450 in 9ce17c1

condition: generator => !generator.reactive && generator.applicationType !== 'uaa' && generator.authenticationType !== 'uaa',

, which means that for a non reactive oauth2 application, the file was written twice.

[mshima]

Great work on config files reorganisation.

Not convinced about the security folder though.
IMO it can be more confusing because we mimic destination package.

Same for database config, having DatabaseConfiguration_cassandra.java.ejs is already clean enough, don't need database/DatabaseConfiguration_cassandra.java.ejs.

[murdos]

I've reverted the move to the security subdirectory and applied the Filename_${option} naming pattern for SecurityConfiguration.java

[mshima]

LGTM

[pascalgrimaud]

I love what you're doing @murdos
It will help a lot for v8, if we decide to use a clean architecture :)

[murdos]

@pascalgrimaud: thanks!
These were a few breaking improvements that I had in mind and wanted to do in a major release, inspired by annoyances or pitfalls that I encountered while working on new features or framework upgrades in generator-jhipster.
I hope indeed that it'll easy maintenance and progress of JHipster 😄