docs: turning store.request document into record(s) is not documented about data

[runspired]

when you use store.request instead of requestManager.request this is automatically done. the result will have a content property that is the json-api document, and its data property will be the record instance.

We make a note of this a few places (for instance under architecture here https://api.emberjs.com/ember-data/5.3/modules/@ember-data%2Frequest and under the main store overview here

data/packages/store/src/index.ts

Lines 121 to 133 in b176861

	* ### Presenting Data from the Cache
	*
	* Now that we have a source and a cach for our data, we need to configure how
	* the Store delivers that data back to our application. We do this via the hook
	* [instantiateRecord](https://api.emberjs.com/ember-data/release/classes/Store/methods/instantiateRecord%20(hook)?anchor=instantiateRecord%20(hook)),
	* which allows us to transform the data for a resource before handing it to the application.
	*
	* A naive way to present the data would be to return it as JSON. Typically instead
	* this hook will be used to add reactivity and make each unique resource a singleton,
	* ensuring that if the cache updates our presented data will reflect the new state.
	*
	* Below is an example of using the hooks `instantiateRecord` and a `teardownRecord`
	* to provide minimal read-only reactive state for simple resources.

) though these spots could be improved and having the api docs for Store.request call this out explicitly would be good.

Note, above 2 should be "2" as in store.request(findrecord('person', '2'));