Remove hardcoded API key from test file

[Copilot]

Commit cca4f18 introduced a hardcoded API key in the test setup, exposing credentials in source control.

Changes:

• Reverted ExampleInstrumentedTest.kt line 43 from hardcoded API key back to empty string

// Before (security issue)
Altude.setApiKey(context,"ak_f8AEgOp8_hLocOBr6S4m6d8xo7T0QKHKB4s2BiamaDc")

// After (restored original)
Altude.setApiKey(context,"")

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[mocolicious]

@copilot is it possible to remove or obfuscate that key from Git history so its not exposed

[Copilot]

@copilot is it possible to remove or obfuscate that key from Git history so its not exposed

I cannot rewrite Git history to remove the API key because:

1. I don't have force-push permissions (required for history rewriting)
2. The API key exists in commit d616c3b which is part of the base branch and the parent PR init fix #18

Recommended actions:

1. Revoke the exposed API key ak_f8AEgOp8_hLocOBr6S4m6d8xo7T0QKHKB4s2BiamaDc immediately and generate a new one
2. A repository admin can use tools like BFG Repo-Cleaner or git filter-repo to remove the key from history:

   bfg --replace-text replacements.txt
   git push --force

3. After history is cleaned, all contributors will need to re-clone the repository

The current commit (10655fd) removes the key from the code, but once a secret is committed to Git, it should be considered compromised and rotated.