fix(angular-standalone): update eslint

[jcesarmobile]

eslint 9 changed the configuration files and .eslintrc.json no longer works.

I first removed all the eslint related packages, .eslintrc.json file and eslint entries from angular.json.
Then ran ng add angular-eslint, which installs eslint-angular and related packages and configure the project with default angular configuration, creating a eslint.config.js and makes some automatic modifications to angular.json.
Then I replaced the no-underscore-dangle rule since it no longer caused issues, but added @typescript-eslint/no-explicit-any as it complains about that now.
Then removed tseslint.configs.stylistic config as it was causing lint errors about empty constructors.
Finally added Page to valid component suffixes since it was causing a lint error that Pages weren't named Component.

I made all the steps as separate commits to see the process better, but should be squashed on merge

closes #1860

[jcesarmobile]

test are falling because the list template uses ev: any.
Not sure if I should add '@typescript-eslint/no-explicit-any': 'off', as vue template does.
Or change the code to

refresh(ev: RefresherCustomEvent) {
    setTimeout(() => {
      ev.detail.complete();
    }, 3000);
  }

or use CustomEvent instead of any as vue/react templates do.

[brandyscarney]

I would use CustomEvent to match our docs but it's up to you.

[jcesarmobile]

I've updated the whole refresher code to match the docs, but I find it weird that it was using the event detail before and now the event target

[brandyscarney]

Yeah it seems like we're inconsistent between the different frameworks:

• Angular
• JavaScript
• React
• Vue

We should update these all to be the same.

[brandyscarney]

I tested this locally and verified that all Angular test apps pass linting without errors. Additionally, introducing a lint error in a test is correctly detected by the linter.

[brandyscarney]

This should pass now with the latest Ionic release.