Fix import classes to call runAllInteractive() rather than runAllViaWeb (which in practice currently just calls runAllViaWeb )

[eileenmcnaughton]

Overview

Fix import classes to call runAllInteractive

Before

Import classes call runAllViaWeb

After

Import classes call runAllInteractive

Technical Details

This is a no-change PR at the moment as it will still call runAsWeb unless the not-yet-viable setting to drive it to the background is used - and we have a gazzillion tests that go through that path.

However, this requires some fixes to instantiate the queue more correctly & stop between-test-leakage on the queue singleton (as was hit by the test with the minor doc-block edit)

Comments

@totten this doesn't address the queue runner screen - but I think with this that is the remaining challenge

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[totten]

@eileenmcnaughton I think these changes look pretty reasonable. Agree that there are other things for background processing to work (but that's OK - because it sits behind an "experimental" feature-flag).

I did a local test run in both modes (default/foreground-runner and experimental/background-runner). For background mode, it was cool to see the background worker actually start doing the job (but not unsurprisingly - it hit an error and then stopped).

For the default/normal mode, it still ran cleanly. 👍 Merging.

[eileenmcnaughton]

baby steps :-)