docs(api): normalize source docstring backticks

[Kemalau]

Why

The docstring source still contains RST-style double backticks across the Python package and CLI, so the docs pipeline has to normalize them at generation time. Cleaning up the source keeps the docstrings consistent with the project's Markdown/Google-style convention and addresses issue #657 directly.

What changed

• replaced RST-style symbol notation with Markdown-style symbol notation in Python string literals under mellea/ and cli/
• kept fenced code blocks intact so literal triple-backtick examples still render correctly
• verified the edited Python sources still compile after the bulk replacement

Verification

• python -m compileall mellea cli
• scanned mellea/ and cli/ for remaining inline double-backtick occurrences after the replacement (only triple-backtick fence literals remain)

Fixes #657

[mergify]

Merge Protections

Your pull request matches the following merge protections and will not be merged until they are valid.

🟢 Enforce conventional commit

Wonderful, this rule succeeded.

Make sure that we follow https://www.conventionalcommits.org/en/v1.0.0/

• title ~= ^(fix|feat|docs|style|refactor|perf|test|build|ci|chore|revert|release)(?:\(.+\))?:

[jakelorocco]

Thanks @Kemalau; I've pinged this issue in another PR that one of our docs maintainers opened to fix this issue in a different way. I think your solution is good; we just need to add a rule to prevent merges with this syntax in the future. We'll see what they say in the other PR.

[planetf1]

Thanks for PR @Kemalau . The intent of the PR looks good - aligned with issue.
I'm suggestionwe merge #658 anyway to get docs working, but also it adds a detection tool.
We'll review this pr (I can't look more until tomorrow) and if good can merge to fix the underlying issue
We already have another issue open to move to hard failures, once the docs are running through the pipeline cleanly, we we prevent future issues.

[planetf1]

Note - We have a template we use for PRs. I suggest copying the format from another PR (use the same comment line at top, section headings, and check boxes from another PR marked as Misc.) Save it. then merge your text back into that format afterwards. That should make the PR Box go green.

[planetf1]

Heads up: 91-file surface area will conflict with #653 on backend files. Recommend merging after #653 and rebasing.

[psschwei]

@planetf1 do we think we could shepherd this over the line now that the doc rewrites are mostly done?

[planetf1]

Thanks @Kemalau for the contribution and for identifying the issue. The PR fell too far behind main to rebase cleanly (206 intervening commits touching many of the same files), so I've opened a fresh branch in #1155 that applies the same fix on current main. Closing this in favour of that PR — your work was the starting point for it.