Disambiguate blueprints by hash instead of name

Nobody has claimed this yet.

This was one thing that tripped me up, while making a custom blueprint, initially the tests weren't properly working, I soon discovered this was because of the fact that blueprints are disambiguated by name.

It's a bit of a foot gun in my opinion, so I'm proposing that the implementation instead hashes these blueprint contents, and then generates them via their hashes, so that any duplicate deployment is deduplicated by their eventual instructions and contents, instead of the name.

I'm using "hash" loosely here, but "an identifier depending on the contents" would work as well.

No files, tests, or entry points are named. Start by locating where blueprints are currently disambiguated by name and how custom blueprints are generated and tested. Done means the project has an agreed content-based identifier strategy and duplicate deployments are deduplicated by their resulting instructions and contents.

Written by the indexing model from the issue text.