A strange seg fault in action

[YaqiWang]

Description of the enhancement or error report

It turns out the error is caused by the code which should be calling _problem->addInitialCondition() but calling _problem->addScalarKernel() due to a copy-paste bug. Although the error should be expected but should not be seg fault inside NonlinearSystem::checkKernelCoverage(). Apparently, MOOSE is happy to treat a scalar IC as a scalar kernel and somehow successfully add it and mess things up.

Rationale for the enhancement or information for reproducing the error

Although I did not try, it should be reproduceable with the input file.

Identified impact

(i.e. Internal object changes, limited interface changes, public API change, or a list of specific applications impacted)
An error detection can be added to avoid such an input error or action error. It will not affect our codes because we are bug free ;-)