Update dependency eslint-plugin-ember to v12 (#856)

* Update dependency eslint-plugin-ember to v12

* disable the problematic ESLint rule for this case

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Jeldrik Hanschke <admin@jhanschke.de>

Author: renovate[bot]

app/helpers/scroll-first-invalid-element-into-view-port.ts

@@ -37,6 +37,13 @@ const scrollFirstInvalidElementIntoViewPort = helper(() => {
     // `schedule('afterRender', function() {})` would be more approperiate but there seems to be a
     // timing issue in Firefox causing the Browser not scrolling up far enough if doing so
     // delaying to next runloop therefore
+    //
+    // This should be refactored at a later point in time to an utility function. At that point
+    // we may consider refactoring it to use a wrapper such as Ember Lifeline easing usage of the
+    // Ember's runloop API. Due to the specifics of this use case - especially calling only native
+    // browser APIs and no Ember code - typical pitfalls of Ember's runloop do not apply in this case.
+    //
+    // eslint-disable-next-line ember/no-runloop
     next(function () {
       const invalidInput = document.querySelector(
         '.form-control.is-invalid, .custom-control-input.is-invalid',

package-lock.json

@@ -91,7 +91,7 @@
     "ember-truth-helpers": "4.0.3",
     "eslint": "8.57.1",
     "eslint-config-prettier": "9.1.0",
-    "eslint-plugin-ember": "11.12.0",
+    "eslint-plugin-ember": "12.5.0",
     "eslint-plugin-n": "16.6.2",
     "eslint-plugin-prettier": "5.2.3",
     "eslint-plugin-qunit": "8.1.2",