Purpose

Some API developers would like to support uniform versions across their API endpoints. Others would like to support per-endpoint versioning. Version transforms could not support uniform versioning when the naming scheme used incremental integer indexes. Instead, transforms will now be defined using indexes which declare the version which is being targeted by the transform.

This allows API developers to select which versioning scheme they would like to support in their project.

If uniform versioning across all endpoints is desired, then newly created transforms should declare the next uniform API version target. Multiple endpoints can 'opt in' to a new uniform version change at the same time by creating transforms for each that target that new uniform version.

We're still able to support per-endpoint versioning, if API developers want to continue incrementing their endpoints' transforms independently of one another.

What does this PR do?

1. Transform loading was modified with the assumption that they are appended by their target version's index.
2. Docs were given some additional explanation about this property of the library.