Reevaluate blueprint swap criteria and implementation

[pheuberger]

The current implementation for querying collection.blueprints.hypercerts seems unclear and may not fully align with intended use cases. Discussions suggest that:

Blueprints fetched via the query may not represent the hypercerts that a collection admin wants in their collection.
The current swapping mechanism (where a blueprint is replaced with a minted hypercert) introduces complexity and may invalidate the purpose of the query in certain scenarios.
There’s a need to revisit the logic for when a blueprint is swapped out, potentially limiting swaps to cases where the metadata is an exact match.

See this thread for more context:
#214 (comment)