Simplify addEntityToModule and document better addAdminRoute.pageTitle

[kaidohallik]

Follow up to #13194 - changes after review from @mshima

---

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.

[mshima]

LGTM

[pascalgrimaud]

@mshima @kaidohallik : all the JDL builds failed, with this stacktrace:

src/main/webapp/app/entities/entity-routing.module.ts:20:88 - error TS2339: Property 'ProductRoutingModule' does not exist on type 'typeof import("/home/runner/app/store/src/main/webapp/app/entities/crm/product/product-routing.module")'.

20         loadChildren: () => import('./crm/product/product-routing.module').then(m => m.ProductRoutingModule),
                                                                                          ~~~~~~~~~~~~~~~~~~~~
src/main/webapp/app/entities/entity-routing.module.ts:25:90 - error TS2339: Property 'CustomerRoutingModule' does not exist on type 'typeof import("/home/runner/app/store/src/main/webapp/app/entities/crm/customer/customer-routing.module")'.

25         loadChildren: () => import('./crm/customer/customer-routing.module').then(m => m.CustomerRoutingModule),

Can one of you have a look plz?
See:

• https://github.com/hipster-labs/jhipster-daily-builds
• https://github.com/hipster-labs/jhipster-daily-builds/runs/1505649488?check_suite_focus=true

[kaidohallik]

microserviceName is missing from this in generator-base.js but is available in files.js (other variables are available in both places). So reverting partially this PR in the new PR shortly.

[mshima]

That's strange.
Not sure why this happened.

[kaidohallik]

Now I checked one more time and problem is that the parameter name is microServiceName but variable in this is microserviceName and I used variable name from this with uppercase S.
Should I create new simplification PR where correct variable name microserviceName is used?

[kaidohallik]

I'll create PR where I rename also all other microServiceName occurrences to microserviceName to avoid such issues in the future.