Include param should always reference array in docs

[Baltazore]

Due to confusion described in #9502 we should update docs and maybe internal usage

TODO:

• Add lint rule with autofix
• Verify all docs updated
• Verify guides updated Draft: [EmberData] Update guides to suggest include to be an array ember-learn/guides-source#2048

[mkszepp]

In you checklist we need to add one point, that we need todo, before we ship lint, updating docs... otherwise api isn't working correctly with includes, when users are using legacy code-parts.

Atm all legacy codes like this.store.findAll / this.store.findRecord are passing include not correctly to api.

When we pass a string[] to include (include: ['comments', 'author']) the urls is:
api/post?include[]=comments&include[]=author

Correctly is:
api/post?include=comments,author

This fix we should also ship to LTS versions, because the current lts are making this mistake

[runspired]

@mkszepp as I said in the ticket, we'd need to look at your particular setup to determine why that is, as that's up to the adapter to do

[mkszepp]

@mkszepp as I said in the ticket, we'd need to look at your particular setup to determine why that is, as that's up to the adapter to do

its not my stetup directly... the bug is already with default json-api adapter (like already told in issue)... here the repo with incorrect api call mkszepp/ember-data-ts-errors@152a105)

Edit:
I think the problem is this code part...

data/packages/adapter/src/-private/utils/serialize-query-params.ts

Line 35 in 3ec0359

buildParams(prefix + '[' + (typeof obj[i] === 'object' && obj[i] !== null ? i : '') + ']', obj[i], s);

for json-api its always correct when its not include as string[], but this code part will be used inside rest-adapter (see https://github.com/emberjs/data/blob/main/packages/adapter/src/rest.ts#L1466), so we need any override inside json-api adapter to fix this

Should we create an additional issue for this bug or do we handel this with my initial issue? Because its not directly part of this PR (only related).

I just wanted to point out in this PR that some other fixes are necessary before we merge this (as it is missing in todo list), because you can't force in docs... to use string[] when its not working with legacy adapter.