Check for currently processing installations (MSI 1618)

(I think this has sort of come up elsewhere for other reasons)

REASONING:
I've had a lot of package installs (MSI - upgrades) failing of late with 1618 meaning MsiExec.exe/InstMsi.exe was already (trying?) installing something else; though I wasn't aware anything else was installing. It might just be a package of my own that is in the creation processes but got "stuck" because the "kinks" haven't been "worked out" yet.

SUGGESTION:
Have choco/cinst/cup.exe check if Windows Installer is already busy before attempting to install package(s) and do some sort of alternative action if Windows Installer is busy. Possibly a statement saying the system is busy already installing programs and abort. Possibly a question asking to delay for X amount of seconds or minutes before continuing. Possibly a default time to wait before processing package installs/upgrades. Possibly a notification and then a loop until Windows Installer is finished. Possibly just continue the attempt of install/upgrade but give a choice after failure to retry? I'm not sure of the best action as I see different options as preferred in instances of manually running choco/cinst/cup versus scripted running of same.

Possibly related to https://github.com/chocolatey/choco/issues/1369?

The issue names no files or tests. Start by reviewing the install and upgrade paths for choco/cinst/cup.exe and the related issue #1369; completion depends on deciding and validating a policy for a busy Windows Installer, such as aborting, waiting, retrying, or prompting.

Written by the indexing model from the issue text.