fix(data): export HttpOptions

[Nosfistis]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngrx/platform/blob/main/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Documentation has been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Other... Please describe:

What is the current behavior?

Any custom implementations of EntityCollectionDataService, particularly those extending DefaultDataService have to import related interfaces with a deep import (e.g. import { HttpOptions } from '@ngrx/data/src/dataservices/interfaces';. Some Typescript compiler option configurations have issues with this, since it is not possible to import from specific files not mentioned in the package.json exports.

What is the new behavior?

Export HttpOptions under @ngrx/data, so that custom EntityCollectionDataService implementations can use it.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[netlify]

✅ Deploy Preview for ngrx-io canceled.

Built without sensitive environment variables

Name	Link
🔨 Latest commit	fc247af
🔍 Latest deploy log	https://app.netlify.com/sites/ngrx-io/deploys/67102ef793f8020008151712

[timdeschryver]

Since we already export QueryParams, which is the deprecated version of HttpOptions I do think this is fine to export.