Feature/add import order rule to eslint

[miettal]

In a96c720, vscode import organize setting is configured.
This PR add same behavior setting to eslint.

1. import/order is import order rule
2. in default, import/order categorize import like builtin, external internal... and these are separate by each group.
3. But vscode import organization setting don't care it. and the function make 1 group.
4. in this setting, this rule customized by definition all import in 1 group to fit vscode import organization setting.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Additional details and impacted files

@@                  Coverage Diff                  @@
##             develop-2024-10-07    #2778   +/-   ##
=====================================================
  Coverage                 56.01%   56.01%           
  Complexity                 8197     8197           
=====================================================
  Files                      2103     2103           
  Lines                     89017    89017           
  Branches                   6560     6560           
=====================================================
  Hits                      49853    49853           
  Misses                    37446    37446           
  Partials                   1718     1718           

[miettal]

Error: src/app/edge/history/shared.ts:3:62 - error TS2305: Module '"date-fns"' has no exported member 'de'.

wow, I just added eslint rules and only did eslint --fix src/. but error is happened. so I convert this PR to draft. I will check it.

[miettal]

Error: src/app/edge/history/shared.ts:3:62 - error TS2305: Module '"date-fns"' has no exported member 'de'.

wow, I just added eslint rules and only did eslint --fix src/. but error is happened. so I convert this PR to draft. I will check it.

This is eslint-plugin-import bug..
import-js/eslint-plugin-import#1479

[lukasrgr]

@miettal are these settings recommended?

[miettal]

I rebased this PR to catch up 2024.10 release.

I'm not familiar with bestpractice for typescript import order rules.
But in fork project, current setting will generate many import order diffs from upstream by using vscode editing. this is bad effect to openems ecosystem. its make difficult to management patchset. this is sure.
So I think unifying import order in all codes and forcing import rule are better.