feat: add support for customizable JADX host in server configuration

[Haicaji]

Pull Request

Related Issues

Closes #

Summary of Changes

• Add configurable target host for JADX plugin communication:
  • Introduce JADX_HOST in config with default 127.0.0.1.
  • Build JADX_HTTP_BASE from host+port instead of hardcoded localhost.
• Add set_jadx_host(host: str) and central URL rebuild helper in config module.
• Export set_jadx_host from server package init.
• Add CLI argument --jadx-host (default 127.0.0.1) in jadx_mcp_server.py.
• Initialize runtime config using host+port before health check.
• Update startup banner fallback output to include configured JADX host.

Testing

• Ran all existing tests
• Added new tests
• Manually tested features

Manual checks performed:

• Python syntax validation passed:
  • python -m py_compile jadx_mcp_server.py src/server/config.py src/server/__init__.py
• Verified argument wiring and config flow in code:
  • --jadx-host parsed
  • config.set_jadx_host(args.jadx_host) invoked before port usage
  • health request base URL uses configured host+port.

Environment note:

• Running python jadx_mcp_server.py --help requires fastmcp dependency in this environment.

Checklist

• My code follows the project’s coding style.
• I have added tests that prove my fix/feature works.
• I have updated documentation where necessary.
• My changes do not break existing functionality.
• I have rebased on the latest main branch.

Additional Notes

Backward compatibility is preserved:

• Existing workflows using only --jadx-port continue to work because default host remains 127.0.0.1.
• This change unlocks remote plugin targeting (e.g., plugin on VM, MCP server on physical host).

[zinja-coder]

I will look into it shortly.