docs: Asset Connectors — concept + Azure DevOps / Bitbucket / GitLab / JSM Assets setup

[devGregA]

Description

Adds documentation for the Asset Connectors feature family to the Pro connectors tool reference:

• A concept section explaining how Asset Connectors differ from findings connectors (asset-inventory reconciliation, NEW/MISSING record lifecycle, automatic Product / Product Type creation, no findings import)
• Tool-specific setup sections for the four new asset connectors, each capturing the auth requirements and platform quirks verified against the live vendor APIs:
  • Azure DevOps — PAT with Code:Read + Project&Team:Read, org-URL formats (incl. legacy visualstudio.com), disabled-repo handling, Cloud-only scope
  • Bitbucket — scoped Atlassian API token requirement (classic tokens are rejected), required workspace slugs (scoped tokens cannot enumerate workspaces), Cloud-only scope
  • GitLab — read_api PAT, self-hosted support, pending-deletion exclusion (deleted projects go MISSING instead of lingering as renamed assets)
  • Jira Service Management Assets — Premium/Enterprise plan requirement, agent-seat requirement, email + token auth

Sequencing note

These document features currently in review: DefectDojo-Inc/connectors #647 #648 #649 #651 and DefectDojo-Inc/dojo-pro #1746 (on the connectors-filters train). This PR should land with or after those.

🤖 Generated with Claude Code

[Maffooch]

Fixed and approving (milestone 3.1.100).

Issue found in review: the new Azure DevOps and Bitbucket sections were inserted between AWS Security Hub's Prerequisites and AWS's own Connector Mappings, which orphaned the AWS us-east-1 endpoint mapping instructions after the Bitbucket section (so "AWS Security Hub → Connector Mappings" no longer read as one entry).

Fix: moved AWS Security Hub's Connector Mappings block back under its Prerequisites. The section order is now clean and alphabetical with each entry intact: AWS Security Hub (Prereqs → Connector Mappings) → Azure DevOps → Bitbucket → BurpSuite.

Verified: re-checked the rendered header hierarchy — every ## tool section is followed by its own #### Prerequisites/#### Connector Mappings, no orphaned blocks. Content is unchanged otherwise. Looks good now.