I've been studying this code to try and get a better understanding of how manifest ordering behaves and I've had a little difficulty understanding what the internal behavior is.

When the end user runs with `--ordering manifest`, how does the behavior of the SequentialPrioritizer instance affect the ordering of resource application?

Perhaps my understanding is being blocked because I've been scanning through the code looking for some behavior similar to what we do with title hashes, but with the manifest file and line number instead of the resource type and title.

This isn't a huge deal or anything, this is really mostly for my own learning and understanding because I've been struggling to understand the behavior of the code.

The main question I'm trying to understand by reading the code is, "Does the ordering of these resources depend on the order they were added to the catalog or does it depend on something else, like the file + line number that is associated with each resource?"