Project Attributes must be in specific order

Currently there is a generic "Attributes" array that is used to store and print the attributes. They have to be in a specific order, so they each need a setter, or else there needs to be a dictionary where each optional one is looked up.

Start by locating the generic "Attributes" array and the code that stores and prints it. Compare the required attribute order with the current output, then determine whether individual setters or keyed lookup best fits the existing design. Done means optional attributes are emitted in the required order and the relevant output behavior is covered by tests, if present.

Written by the indexing model from the issue text.