What does this PR do?

Hover content is rendered as Markdown, so plain-text schema descriptions must be escaped for Markdown. The current escaping escapes punctuation like . and (), which can, for example, change a URL at the end of a sentence into https://hub\.docker\.com/\.. When the text is being auto-linkified by the hover renderer, it then include the backslash in the auto-detected link, making it end with \ and become unusable (for example, https://hub.docker.com/\).

This is fixed by updating YamlHover.toMarkdown() to stop escaping punctuation commonly used with URLs i.e. . ( ).

Note: Best practice is for schemas to wrap URLs in <...> (for example, <https://example.com>), so the renderer treats them as explicit autolinks and they reliably stay usable.

What issues does this PR fix or reference?

• Some links are escaped making them unusable #1151

Is it tested? How?

Automated test:

• Added hover tests to ensure () parentheses and . dots remain literal even without escaping in descriptions.
• Added hover tests to ensure URLs next to () or . stay usable.

Manual test:

• Create a file .github/workflows/daily.yaml
• Add content:

  name: Daily
  
  on:
    schedule:
      # Runs daily at 10:15 CET (09:15 UTC)
      - cron: '15 9 * * *'
    workflow_dispatch:  # Allow manual triggering
  
  jobs:
    update-data:
      runs-on: ubuntu-latest
      
      steps:
      - name: Checkout repository
        uses: actions/checkout@v4

• Hover over to the text actions/checkout@v4. Links in there should be usable.