[facelessuser]

1. Ensure start is only adjusted with the longest closing code span is less than the opening and greater than 0.
2. Remove dead code as we should always find an opening.
3. find_code_span will always return an opening. End will be None if a match could not be found.
4. Ensure the beginning backticks are not parsed again if no end was found.

Fixes #1668

Description

AI Assistance Disclosure

• No AI tools were used in preparing this PR.

• AI tools were used and I have disclosed which ones, and have fully reviewed and verified their output.

  AI tools were use to assist with the following:

  • Code
  • Code Comments
  • Documentation
  • Changelog Entry
  • Commit Message
  • The Description Above
  • Other: ______________

Checklist

• This PR follows the contribution guidelines.
• The code follows the Code Style Guide.
• The commit message follows the Commit Message Style Guide.
• I have added or updated relevant docs, including release notes if applicable which follow the Documentation Style Guide.
• I have added or updated relevant tests.
• I have not requested, and will not request, an automated AI review for this PR.

[waylan]

I have noticed this in a few of your recent PRs. Every entry in a changelog must be nested under a level 3 heading of either Fixed, Changed, Added, or Removed. You keep leaving that out, which causes deployment to fail when our deploy script attempts to extract the release notes from the changelog. I don't know why the changelog validator doesn't catch it in a non-release. I fixed it hear when I resolved a merge conflict, but I wanted to bring it to your attention.