[PE] migrate printStackTrace to proper logging (flutter#8116)

Inspection description:

> Reports calls to Throwable.printStackTrace() without arguments.
Such statements are often used for temporary debugging and should be
either removed from the production code or replaced with a more robust
logging facility.

Note that this PR disables the inspection in TEST scopes since
`printStackTrace()` is handy there and "robust" logging in a test
context is often more of a hinderance than help.

---

- [x] I’ve reviewed the contributor guide and applied the relevant
portions to this PR.

<details>
  <summary>Contribution guidelines:</summary><br>

- See our [contributor
guide]([https://github.com/dart-lang/sdk/blob/main/CONTRIBUTING.md](https://github.com/flutter/flutter/blob/main/docs/contributing/Tree-hygiene.md#overview)
for general expectations for PRs.
- Larger or significant changes should be discussed in an issue before
creating a PR.
- Dart contributions to our repos should follow the [Dart style
guide](https://dart.dev/guides/language/effective-dart) and use `dart
format`.
- Java and Kotlin contributions should strive to follow Java and Kotlin
best practices
([discussion](flutter#8098)).
</details>

Author: pq

.idea/inspectionProfiles/Project_Default.xml

@@ -163,7 +163,7 @@ public void flushFlutterErrorQueue() {
         }
       }
       catch (InterruptedException e) {
-        e.printStackTrace();
+        LOG.error(e);
       }
     }
   }