Allow users to specify different contract test inputs for each individual test / new resource

I am developing a resource that requires a real, unique activation key as one of its properties.

I have to override inputs because I need to specify real activation keys; a fake key will be rejected. But, I can only specify a single override value, which causes the same key to be reused across tests when running contract tests using `cfn test`.

I can somewhat get around this by running a single contract test at a time and changing the inputs one at a time.

In this case, it would help if I could specify a set of input values so that a different key is chosen for each resource created by the contract tests, and keys aren't repeated.

Comienza rastreando cómo `cfn test` lee y aplica las sobrescrituras de entrada de los contract tests. Determina dónde podría asociarse un conjunto de valores con pruebas individuales o recursos creados y, después, verifica que cada recurso reciba una clave distinta sin reutilización durante la ejecución de los contract tests.

Escrito por el modelo de indexación a partir del texto del issue.