test: add Xquik OpenAPI fixture

[kriptoburak]

Summary

• Add a compact Xquik OpenAPI 3.1 fixture that covers API key security, optional bearer auth, query parameters, and paginated response schemas.
• Add e2e coverage to verify info, path listing, component listing, and operation detail access for the fixture.

Validation

• npm run build
• npx jest test/__tests__/e2e/spec-loading.test.ts --runInBand
• npm run format:check

Duplicate check: no existing Xquik fixture or matching open or closed PR found before opening this PR.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 11 complexity · 0 duplication

Metric	Results
Complexity	11
Duplication	0

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[kriptoburak]

If this is useful and you merge it after checks pass, feel free to share the PR on X/Twitter and mention my handle, burakbayir. I can repost or retweet it to my 24k followers of developers and power users, which may help more relevant users discover this repo.

[kadykov]

Hi @kriptoburak, thank you for the follow-up and for the generous offer to share the project with your community!

Regarding the PR: as mentioned previously, I have a strict policy of using brand-neutral fixtures (like example.com) in the codebase to ensure the project remains focused on the tool's functionality and avoids commercial branding.

However, I agree that the technical cases you've identified—specifically the security schemes and paginated responses—are valuable additions to our test suite. Because of this, I have created a new PR #197 that implements these specific test cases using generic, brand-neutral fixtures.