Finish deprecating 'Update Manager' related code in Update Status

Minor comments.

Thanks! Applied suggestions. Leaving the thread about moving the test into a new class open to see if anyone else has a strong opinion.

Thanks to our new gitlab bug I can't drill down into the test failures.

There are no failures. The failure was the pipeline never started. Longwave and Drumm seem to have sorted it out.
I’ll push a no-op commit to hopefully trigger a new pipeline.

Yay, the pipeline really ran. However, there seem to be failures, after all. 😂 I’ll look more closely when I’m at my laptop.

Was calling the deprecated method from hook cron, which caused any tests that enable update.module and invoke cron to trigger deprecation notices. Removed that from cron, and now the pipeline is all green. Back to NR.

What is the full status of this initiative? Does this change need a CR?
If this piece is just clean up then I think we're ok, however, since we're deprecating things I think we need to notify people that disk cleanup won't happen anymore.

All the new deprecations reference the CR from the parent issue. If we’re happy and this lands, I’ll update that CR to mention these other deprecations. Assuming this ships in 11.2, seemed silly to use a separate CR for it. See the parent issue and linked CR for more.

Thanks!
-Derek

p.s. This specific disk cache cleanup method is only cleaning up a cache of tarballs downloaded for the deprecated and removed “Update Manager” stuff. So nothing would be populating this cache, so no need to garbage collect it.

12 answers my question, I thought that was true, but wanted confirmation.

To make #11 explicit, adding the tag. I hereby solemnly swear to make the updates once this is committed...

Added a remaining task, probably for release managers:

Decide if we should explicitly mark the allow_authorize_operations setting itself deprecated in sites/default/default.settings.php and core/assets/scaffold/files/default.settings.php