contract_tests: contract_create_read_success and primaryIdentifiers in responses

When a customer wants to create a our resource, he sends a request like so:

```json
{
"ourObj": {
"someProp": "someValue"
}
}
```

And our API, upon successful creation, will return the following:

```json
{
"ourObj": {
"someProp": "someValue",
"id": "ourJustGeneratedObjId"
}
}
```

It seems that there is no way at all to pass the contract-tests with this schema. Passing a hard-coded value for `ourObj.id` does not make sense, as the delete test will fail.

I've worked around the `contract_create_delete` failure by copying `ourObj.id` to another property in the schema:

```json
{
"CfnId": "ourJustGeneratedObjId",
"ourObj": {
"someProp": "someValue",
"id": "ourJustGeneratedObjId"
}
}
```

`CfnId` is set as the `primaryIdentifier`.

This way, the model sent in the request is returned back in the response - none have the `ourObj.id`. However, our customers may be relying on the existence of this `id` inside `ourObj`.

What can be done about this?

Inizia leggendo i test contract_create_read_success e contract_create_delete, quindi segui come vengono gestiti primaryIdentifier e primaryIdentifiers nello schema contract-test. Confronta gli esempi di request e response con le aspettative del test di delete e definisci il comportamento previsto per gli identificatori generati prima di modificare qualsiasi cosa.

Scritto dal modello di indicizzazione a partire dal testo della issue.