Add a Problem boolean parameter to skip initial conditions when restarting

[YaqiWang]

Motivation

Both restarting and initial conditions can be used to initialize variables. Initial conditions act after the restart. Currently, if both exist, MOOSE will issue an error to let users know there is a competing condition for initializing variables. Users can then set Problem/allow_initial_conditions_with_restart=true to deliberately let the initial condition overwrite the values set by the restart. It can be desired the other way around, i.e. ignore the initial condition. Sometimes, users just want to try a restart file quickly without having to delete existing initial conditions which can be tedious or difficult if the number of initial conditions is large and/or they are set by a custom action.

Design

I suggest we add another control parameter Problem/skip_initial_condition_when_restarting for this. Its default value will be false, and when it is set to true, it also turns on Problem/allow_initial_conditions_with_restart=true. The code should only ignore those initial conditions whose targeting variables are restarted. It is possibly desired to add a screen output to show how a variable is initialized like

var1 none (zero)
var2 restarted
var3 IC:ic1,ic2

Impact

Allow users to have more control on how to initialize variables with restart.

[GiudGiud]

The code should only ignore those initial conditions whose targeting variables are restarted

so Problem/skip_initial_condition_when_restarting is not a good name.
Maybe Problem/prioritize_variable_restart_over_initial_conditions or something