v3.10.3 -- Opt-in Claude integration, DLL licensing compliance

What's new in 3.10.3

Claude Code integration is now fully opt-in

pbi connect no longer writes to ~/.claude/ automatically. The new setup flow is:

```bash
pipx install pbi-cli-tool # 1. Install
pbi-cli skills install # 2. Register Claude Code skills (shows what will be written, asks y/N)
pbi connect # 3. Connect to Power BI Desktop
```

A new pbi-cli entry point handles Claude Code setup. pbi-cli skills install/uninstall/list are the explicit management commands. pbi connect prints a one-line tip if skills are not yet installed, but never writes anything.

DLL licensing compliance

The Microsoft Analysis Services client library DLLs bundled in src/pbi_cli/dlls/ are now correctly attributed under Microsoft's own license terms — not sublicensed under MIT. The wheel now ships:

• THIRD_PARTY_LICENSES.md — full verbatim Microsoft Software License Terms (EULA)
• NOTICE — short-form attribution for the 5 bundled DLLs
• src/pbi_cli/dlls/README.md — in-directory sentinel

pyproject.toml uses the PEP 639 SPDX expression MIT AND LicenseRef-Microsoft-AS-Client-Libraries.

SECURITY.md rewrite

• Supported versions table updated to 3.10.x
• Architecture section: accurate description of direct pythonnet/.NET interop (no MCP server, no subprocess)
• Global Configuration Modifications section updated to reflect the opt-in model

Upgrading

```bash
pipx upgrade pbi-cli-tool
```

If you had skills installed from a previous version, they remain in ~/.claude/skills/. Run pbi-cli skills install --force to refresh them to the latest versions.

Full changelog

See CHANGELOG.md for the complete history.