chore: post-transfer cleanup (Wandera → Jamf migration)

[dtpryce]

Wandera → Jamf Migration: Post-Transfer In-Repo Cleanup

Updates all Wandera org references after the repository transfer.

Changes

• CODEOWNERS — @wandera/datascience → @jamf/data-science
• setup.py — GitHub repo URL updated
• README.md — badge URL updated; CodeQL badge removed (workflow was deleted)
• CONTRIBUTING.md — issue links updated
• onepassword/client.py — wandera.1password.com account domain examples updated to jamf.1password.com
• codeql-analysis.yml — deleted (was already staged for removal)

⚠️ Post-merge manual steps

1. Re-encrypt and set GHA secrets in Jamf org: PYPI_API_TOKEN, TEST_PYPI_API_TOKEN
2. Configure Jamf team access (datascience team — teams do not transfer automatically)
3. Verify CI passes on first push
4. Update JAMS Dependabot if flagged: https://maps.engops.jamf.build/dependabot
5. Update JAMS ORCA if flagged: https://maps.engops.jamf.build/lacework
6. Change repo visibility from public to internal if desired (was not TF-managed — must be done manually in GitHub Settings)

[dtpryce]

1. Re-encrypt and set GHA secrets in Jamf org: PYPI_API_TOKEN, TEST_PYPI_API_TOKEN - not needed already checked CI and it works
2. Configure Jamf team access (datascience team — teams do not transfer automatically) - done
3. Verify CI passes on first push - see above
4. Update JAMS Dependabot if flagged: https://maps.engops.jamf.build/dependabot - done
5. Update JAMS ORCA if flagged: https://maps.engops.jamf.build/lacework - no need
6. Change repo visibility from public to internal if desired (was not TF-managed — must be done manually in GitHub Settings) - done