eslint indiscriminately errors for `.reload()` and `.save()`

[mkszepp]

With latest ember-cli-update (v6.10.0+) there were added eslint rules for warp-drive.

Unfortunally we have some issue, like controller.relaod() or a service with this.myService.reload() or window.location.reload(); it comes as error that we should not use warp-drive/no-legacy-request-patterns.

The same thing we have with local functions in components like this.save()

Also the await fetch(url, options); brings error Use store.request() instead of fetch() warp-drive/no-external-request-pattern

[runspired]

• controller.reload being linted against is intentional, as reloading requests is preferred
• navigation.reload() is accidental, been meaning to fix that
• <not-data-thing>.reload() and <not-model>.save() can only be avoided if we move to far more expensive type-aware lints. These APIs tend to be used so rarely outside of making requests, it seems better to accidentally catch them in the request infra to encourage clear naming etc. than to pay the perf cost in the lints. Open for debate though.
• raw fetch is linted against by design. As is ajax and any number of related ajax-like APIs.

[mkszepp]

• controller.reload being linted against is intentional, as reloading requests is preferred

in my case there is a custom reload function on controller which makes more than just a request with warp-drive...

* `<not-data-thing>.reload()` and `<not-model>.save()` can only be avoided if we move to far more expensive type-aware lints. These APIs tend to be used so rarely outside of making requests, it seems better to accidentally catch them in the request infra to encourage clear naming etc. than to pay the perf cost in the lints. Open for debate though.

False positive lint rules are in my eyes bad, when they will be forces as recommended (in ember, the eslint rules, which are bringing false positive results were never forced as recomended). In the current situation this lint rules must be disabled in most of the apps, because only checking for keyword .reload or .save is not really a super idea.

We have disucssed on Discord about peekAll and peekRecord.
Right now they were landed in same lint rule like all legacy request parts (warp-drive/no-legacy-request-patterns). Is there possible to create for them a extra lint rule, because they do make no request, are not depreacted... (legacy-request is in my eyes everything which works with serializer/adapters/transforms and which will disabled with store option legacyRequests: false)