SSA ANDI Tool Removed From Production CRASM-3002

[RKohler21]

🗣 Description

Ensure SSA ANDI tool references and access are removed from production environment configurations and code, while preserving them in all development environments.

💭 Motivation and context

As a developer, I want the SSA ANDI tool integrations (located in api.js, docs.js, and settings.py) to be excluded from the production environment, so that sensitive or dev-only tools do not impact production performance, security, or stability.

🧪 Testing

Still needs testing in production environment to confirm removal of access to SSA ANDI Tool references

✅ Pre-approval checklist

• This PR has an informative and human-readable title.
• Changes are limited to a single goal - eschew scope creep!
• All future TODOs are captured in issues, which are referenced in code comments.
• All relevant type-of-change labels have been added.
• I have read the CONTRIBUTING document.
• These code changes follow cisagov code standards.
• All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• Tests have been added and/or modified to cover the changes in this PR.
• All new and existing tests pass.
• Bump major, minor, patch, pre-release, and/or build versions as appropriate via the bump_version script if this repository is versioned and the changes in this PR warrant a version bump.
• Create a pre-release (necessary if and only if the pre-release version was bumped).

✅ Pre-merge checklist

• Revert dependencies to default branches.
• Finalize version.

✅ Post-merge checklist

• Create a release (necessary if and only if the version was bumped).

[jsalinasnttdata]

LGTM

[ameliav]

Will need to be tested in Production for confirmation

[rapidray12]

Simple change. LGTM