Profile Headers for 1.0 Requests

For a response which is processed using the v1 1.0 profile expectation (ex reading `new_obj_state`), the request must contain a Profile header request for the response under the v1.1 profile.

Ex.
```HTTP
Request:
POST /v1/create HTTP/1.1
Content-Type: application/json
Profile: http://storedev.rerum.io/profile1.0
body {"hello":"world"}

Response:
HTTP/1.1 201 Created
Content-Type: application/json
Accept-Profile: http://storedev.rerum.io/profile1.0
body {"@id":"https://example.item/id/123", "hello":"world", "new_obj_state":{...}}
```

Start with issue #24 and its HTTP request/response example, then locate the API entry point that processes v1 requests and profile expectations. Confirm the intended Profile and Accept-Profile behavior for responses containing new_obj_state, and consider the work complete when the behavior is covered by an executable request/response check.

Written by the indexing model from the issue text.