Remove duplicate `RequestOptions` imports in access service

[Lakes41]

Difficulty: Hard

Type: Bug

Summary

Fix duplicate RequestOptions imports in the access service and add a lint rule or typecheck guard to prevent similar import conflicts.

Current Behaviour

src/access/access.service.ts imports RequestOptions from both ../http/http.types and ../types/common. This can produce TypeScript duplicate identifier errors or hide which request option contract the service should use.

Expected Behaviour

The access service should import one canonical request options type, and the project should catch duplicate imports during CI.

Suggested Implementation

Decide which module owns the public request options type, update the access service import, and add an ESLint or TypeScript check that prevents duplicate imports and unused imports.

Files or Areas Likely Affected

• src/access/access.service.ts
• src/http/http.types.ts
• src/types/common.ts
• eslint.config.*
• package.json

Acceptance Criteria

• AccessService imports RequestOptions from one canonical module
• Typecheck passes without duplicate identifier errors
• Linting catches duplicate imports where possible
• Other services use the same request options type
• Tests or CI commands verify the corrected import structure
• No public method behaviour changes are introduced

Additional Notes

This is intentionally scoped to type hygiene and build stability.

[nelly439]

I'd like to take this issue.

I have experience maintaining TypeScript SDKs and improving type safety across service layers. I can consolidate RequestOptions into a single canonical type, remove the duplicate import conflict in AccessService, update any affected services to use the same contract, and add lint/typecheck safeguards so similar issues are caught automatically in CI. The changes will be limited to type hygiene and build stability, with no impact on the public API or runtime behavior.

[grantfox-oss]

🦊 GrantFox — @nelly439 has been assigned to this issue as part of the Official Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #83)
2. Your PR will be reviewed by the Adamantine-guild maintainers

Good luck! Track your progress on GrantFox.