Add alternative error tagging class

[drummerdoc]

This PR introduces an alternative to ErrorRec/ErrorList for managing error tagging. It supports building (GPU-SAFE) tagging functions on the fly via ParmParse inputs, something like:

amrex::Vector<amrex::AMRErrorTag> errtags;
errtags.push_back(AMRErrorTag(value,AMRErrorTag::GREATER,field,info));

Then later, they are called to tag as:

  for (int j=0; j<errtags.size(); ++j) {
    std::unique_ptr<MultiFab> mf;
    if (errtags[0].Field() != std::string()) {
      mf = std::unique_ptr<MultiFab>(derive(errtags[j].Field(), time, errtags[j].NGrow()));
    }
    errtags[j](tags,mf.get(),clearval,tagval,time,level,geom);
  }

At the moment, standard support is provided for BOX (over physical region), LESS, GREATER, GRAD, as well as a special one, VORT, for vorticity over AMR levels. and USER. USER is close to AMReX-classic error tagging functions. In the initial implementation, the inputs can specify a start and stop time, max level for each criteria to apply to, the field to base the decision on, and a physical box to limit the checking. ParmParse input can be organized as follows, e.g.:

amr.refinement_indicators = flame_tracer lo_temp
amr.refine.flame_tracer.max_level = 3
amr.refine.flame_tracer.value_greater = 1.e-6
amr.refine.flame_tracer.field_name = Y(H)

amr.refine.lo_temp.max_level = 2
amr.refine.lo_temp.value_less = 1000.
amr.refine.lo_temp.field_name = temp

This will tag regions up to level 3 where Y(H)>1.e-6 and up to level 2 where temp<1000.

[WeiqunZhang]

The functionality looks great. I have some minor comments.

[ax3l]

@drummerdoc @WeiqunZhang Getting a AppleClang (SP) and DPC++ (DP) compile error on this of the form:

Src/AmrCore/AMReX_ErrorList.cpp:318:52: error: non-constant-expression cannot be narrowed from type 'double' to 'float' in initializer list [-Wc++11-narrowing]

in WarpX.

[ax3l]

maybe we can cast the i, j, k with Real(i) etc. and add _rt in + 0.5 as + 0.5_rt to fix it.

[ax3l]

Let's try this: #1180