feat: Add guardrails to restrict destructive Artifactory tools via env vars

[dimatcimbal]

Summary

• Introduces JFROG_READ_ONLY_MODE=true — drops all 14 write/delete tools at server startup, preventing the LLM from calling any mutating Artifactory operations
  (create/update/delete repos, permissions, projects, release bundles)
• Introduces JFROG_TOOLS=<comma-list> — allowlists specific tools by name, stacking with the read-only filter for precise per-deployment control
• Fixes a pre-existing TypeScript compile error in common/utils.ts: content-type header typed as a union including number, which lacks .includes() — cast to string to
  unblock strict-mode compilation
• Removes unreachable return response.data after return postProcess(response.data) in common/utils.ts

Usage

  # Allow only read operations
  JFROG_READ_ONLY_MODE=true

  # Restrict to specific tools only
  JFROG_TOOLS=jfrog_execute_aql_query,jfrog_list_repositories,jfrog_get_artifacts_summary

[github-actions]

Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request. Posted by the CLA Assistant Lite bot.}