Microservice without user management shall not generate User and Authority entities as well as related resources

[ko5tik]

This PR fixes #18755 - (not)generation of user administration artifacts. Currently when 0Auth2 is actoivated user entotoes and
supporting classes are generated for all backend microservices even if they have this feature explicitely switched off
in .yo-rc.json

Proposed behaviour is to honor explicit settings ( which is generated into .yo-rc.jason by default anyway )

---

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

[ko5tik]

I see that there is a bug, update will follow soon

[ko5tik]

@DanielFran, @mshima since it seems to be your use case - there is pipeline error, in [ms-ngx-eureka-oauth2-mongodb-caffeine - because oauth2 does not activate user entity generation atuomatically. Not sure how to fix it

• explict setting in the pipeline for "skipUserManagement false" , or implicit activation in case there is relation to user entity.

[CLAassistant]

All committers have signed the CLA.

[DanielFran]

@ko5tik @mshima I believe that this has already been fixed on main branch. Can you confirm?

[mshima]

@DanielFran no, but we should this PR can be closed. There is a full application in it.
Since no database is fixed without the User entities, it should be easier to implement now.

generator-jhipster/generators/base/generator-base-todo.mjs

Lines 1073 to 1077 in 6ec1bf9

	// TODO make UserEntity optional on relationships for microservices and oauth2
	// TODO check if we support syncWithIdp using jwt authentication
	// Used for relationships and syncWithIdp
	const usesSyncWithIdp = dest.authenticationType === OAUTH2 && dest.databaseType !== NO_DATABASE;
	dest.generateBuiltInUserEntity = dest.generateUserManagement || usesSyncWithIdp;

I will post the comment at the issue for reference.
Closing the PR for now, once cleaned please reopen.