Disambiguate blueprints by hash instead of name

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 se nombran archivos, pruebas ni puntos de entrada. Empieza por localizar dónde se desambigüan actualmente los blueprints por nombre y cómo se generan y prueban los blueprints personalizados. El trabajo estará terminado cuando el proyecto haya acordado una estrategia de identificadores basada en el contenido y los deployments duplicados se dedupliquen según sus instrucciones y contenidos resultantes.