Fix characters interpreted as Smithy format specifiers in doc gen

[arandito]

Description

Fixed an issue in doc string generation where special characters (specifically $) in the Smithy model's documentation traits were being incorrectly interpreted as Smithy format specifiers (docs).

The fix adds the $L formatter to write() and writeInline() calls in MarkdownToRstDocConverter.java, ensuring doc strings are treated as string literals rather than as format expressions. This prevents the unintended interpolation of doc strings that contain characters like $.

Testing

Successfully rebuilt aws-sdk-bedrock-runtime client and ensured no changes were reflected in docstrings.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[jonathan343]

Thanks for this PR!

I think this looks good. We should consider adding some test coverage to this file: https://github.com/smithy-lang/smithy-python/blob/3c3bacffdcfeda6dfede98a780e107a60bb8ac4f/codegen/aws/core/src/test/java/software/amazon/smithy/python/aws/codegen/MarkdownToRstDocConverterTest.java. Maybe something simple like being able to handle the $ character and any other cases you're aware of

[ubaskota]

LGTM. Please, address Jonathan's comments before merging.

[arandito]

Added a unit test to cover case where HTML string has the character $. This will also cover any future format specifiers as we are treating the entire string as a literal.

Ran make build-java to ensure test fails with the current state on develop and that it passes with the PR fix.

[jonathan343]

LGTM, thanks Antonio!