Batch API assumes client's support of meta refresh

@catch since ✨ Add an 'instant' queue runner Needs work is closer then this should this one be closed?

That issue starts giving us more options to process queues but it doesn't do anything to convert or fix batch API. For genuinely very long running tasks that need to be completed in a short time (installing and uninstalling modules etc.) it won't help at all.

For the lynx case where there's an interactive browser that supports neither javascript nor meta refresh, the original idea of outputting a link for the user to click makes sense - the usual 'Click this link if you are not automatically redirected' sort of thing.

For everything else we have more recent, but still old, issues like 📌 Make batch a wrapper around the queue system Needs work

Given the age of this issue and the lack of +1s from anyone affected by this bug, can we safely assume that anyone who wants to use Batch API either has JS enabled or uses a browser that supports meta refresh? Is there really anyone still using Drupal in Lynx? I assume there is no modern browser that allows meta refresh to be disabled either.

The issue I can see with 'Click this link if you are not automatically redirected' is that people might click it anyway if they see a link, which I think risks breaking the batch process more than if they just left it alone, which is the correct thing to do in 99.9% of cases.

Overall, I vote this is closed as won't fix.

#31 makes sense, let's do that. Anyone that was trying to administer a Drupal site using lynx is already able to do everything they want via the command line.