fix(query): Add export to _CreateBaseQueryOptions type

[Arthie]

PR Checklist

Please check if your PR fulfills the following requirements:

• The commit message follows our guidelines: https://github.com/ngneat/query/blob/master/CONTRIBUTING.md#commit
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)

PR Type

What kind of change does this PR introduce?

• 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?

I'm migrating from v1 to v2 and encountered this error:
Return type of public method from exported class has or is using name '_CreateBaseQueryOptions' from external module "node_modules/@ngneat/query/lib/base-query" but cannot be named. ts(4053)
Typescript can't name the return type of 'queryOptions' function in a public class method.

Here is a code example:

@Injectable({ providedIn: 'root' })
export class ExampleClientService {
    private httpClient = inject(HttpClient);

    queryUser(id: string) {
//  ^? error: Return type of public method from exported class has or is using name '_CreateBaseQueryOptions' from external module "node_modules/@ngneat/query/lib/base-query" but cannot be named.ts(4053)
        return queryOptions({
            queryKey: ['USER', id] as const,
            queryFn: () => {
                return this.httpClient.get(`/user/${id}`);
            },
        });
    }
}

Issue Number: N/A

What is the new behavior?

No more typescript errors when using "queryOptions" function return type in a public class method.
Adding export to the _CreateBaseQueryOptions interface fixes the typescript error.

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[NetanelBasal]

I'm wondering why it happens only to you

[Arthie]

It's because of the typescript's declaration compiler option. I assume it enables stricter rules, since typescript wants to include an import to the '_CreateBaseQueryOptions' type for the generated .d.ts file.

"compilerOptions": {
    "declaration": true
  },

If I set declaration to 'false' I don't get the error.
Setting 'declaration' to false solves my issue. This PR can be closed unless you want to fix it for 'declaration' true as well.

[NetanelBasal]

Why do you need declaration true in applications?

[Arthie]

Correct, you don't need declaration true in applications. However, declaration:true is the default setting for angular libraries generated with nx in our monorepo. We might want to publish those libraries with .d.ts files, so multiple applications can use them.