Add preparation flag related to sub id to name map

[lindsayad]

And make sure we do sync the map when we're completing preparation

[moosebuild]

Job Coverage, step Generate coverage on facfa4b wanted to post the following:

Coverage

Inconsistent report tags were found between the head and base reports.
This can happen when reports are missing from either the head or the base.

Inconsistent tags:
32bit-np2_threads2
Full coverage report

This comment will be updated on new commits.

[roystgnr]

At first glance it looks like we just need to fix up downstream use cases before we can rebase this and retry CI ...

But at second glance, it looks like at least some of those failures downstream are because we're e.g. asserting _mesh->is_prepared() where we should only be asserting _mesh->_preparation.has_boundary_id_sets? We might be able to fix that here; I could push a commit to try, if my comment here isn't clear enough.

[roystgnr]

Huh. Now I'm seeing is_prepared() assertions failing in DofMap, and I don't actually want to weaken those. We really shouldn't be getting to DoF numbering or renumbering without a prepare_for_use() (or ideally complete_preparation()) first, and I'm not sure how we are.

[lindsayad]

Those failures will be fixed by idaholab/moose#33276, so we can wait for that to make it to MOOSE master and then invalidate here

[lindsayad]

Might not have needed to force push to revert a commit just added into devel, but I did. facfa4b is the only new commit since @roystgnr's last comment

[lindsayad]

This will still fail until idaholab/moose#33276 makes it into master