Always import users first, if you can

Problem/Motivation

A user reported an issue in Slack where some Shortcuts and Path Aliases were not able to import until the anonymous user was imported. A core issue related to this can be found here: https://www.drupal.org/project/drupal/issues/3057399

Steps to reproduce

Build the Tome site found in this commit (/drupal folder) https://github.com/Decipher/druxt-experiments/commit/fb3679eae2b3f619008..., or get yourself into a situation where a content entity is missing a dependency to the anonymous user in meta.json.

Proposed resolution

While we could add the anonymous user as a dependency for, well, everything, I think the best choice would be to prioritize importing users first, if we can. By that I mean if a user has no other dependencies, try to import it. At the very least I think this should always import the anonymous user just fine.

Remaining tasks

Write a patch.

User interface changes

None.

API changes

None.

Data model changes

None.