make application stop to be a request in the application controller

[TheGeorge]

Application start is already a request, and this change make stop one as well. This ensures
that the application controller isn't blocked during application shutdown.

[github-actions]

CT Test Results

    2 files     70 suites   1h 9m 31s ⏱️
1 569 tests 1 326 ✅ 241 💤 2 ❌
1 820 runs  1 526 ✅ 292 💤 2 ❌

For more details on these failures, see this check.

Results for commit 619fb5c.

♻️ This comment has been updated with latest results.

To speed up review, make sure that you have read Contributing to Erlang/OTP and that all checks pass.

See the TESTING and DEVELOPMENT HowTo guides for details about how to run test locally.

Artifacts

• Complete CT logs (Download Logs)
• HTML Documentation (Download HTML Docs)
• Windows Installer

// Erlang/OTP Github Action Bot

[michalmuskala]

I think we need to track stopping applications (and the stopper processes) properly to avoid the same issue as in #9494.
In particular, during termination, if an application started stopping, we should wait until it finishes before we stop any of its dependencies. I think this PR as implemented could violate that, since we don't track the stopping applications in terminate

[TheGeorge]

The change currently keeps only track of stopping applications, but not the stopper. Semantically, there is currently no change to the status quo when using the API from the application module.

From the application controller point of view, when it comes to stopping, there is no dependency between applications, and they can be stopped independently right now. (regardless of the PR)

[TheGeorge]

I ran the failing test suite and test locally, but cannot reproduce the failure.

[garazdawi]

I've retriggered the tests to see if the error persists.