Remove deprecated JHipster Console (ELK)

[PierreBesson]

As the JHipster Console has not been upgraded in over a year. I'm removing the options from deployment subgens. I will change our documentations to replace them with generic instructions to connect JHipster apps to a generic a ELK setup.

---

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

• All continuous integration tests are green
• Tests are added where 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.

[pascalgrimaud]

Really sad but I totally understand, as we work during our freetime, it's hard to maintain it for years :)

[PierreBesson]

Not only too much work to maintain but also in retrospect I think it was a mistake to want to do everything as part of the JHipster project including providing our own deployments for the monitoring stack. Also, the world has changed a lot in the 5 years since releasing the Console and most people's focus has shifted to the Cloud and managed services. Also, it's not possible to guarantee good security with the current Console (no security patches, no encryption when forwarding logs, etc).

[pascalgrimaud]

you have some prettier format to do

[PierreBesson]

Thanks a lot @pascalgrimaud for fixing things for me !

[pascalgrimaud]

@PierreBesson : you're welcome, my friend ! :) it's team work !