Feedback Form Bugs: Not rendering markdown and feedback button click not persisting

[lexi-taylor]

Description

• When the disclaimer has markdown (bold, italic, links, etc), the feedback form was not rendering the markdown as expected.
• When a user submits feedback, the feedback button click was not persisting, making it appear like feedback was never submitted by the user

Specific Changes

1. Added support for markdown in the disclaimer by calling the useRenderMarkdown hook
2. Ensure feedback button clicks are persisted by not resetting the feedback action state once submit has been pressed. This required introducing a new variable for when feedback has been submitted
3. Deleted some flaky tests which fail occassionally with the tooltip over the feedback button

• I have added tests and executed them locally
• I have updated CHANGELOG.md
• I have updated documentation

Review Checklist

This section is for contributors to review your work.

• Accessibility reviewed (tab order, content readability, alt text, color contrast)
• Browser and platform compatibilities reviewed
• CSS styles reviewed (minimal rules, no z-index)
• Documents reviewed (docs, samples, live demo)
• Internationalization reviewed (strings, unit formatting)
• package.json and package-lock.json reviewed
• Security reviewed (no data URIs, check for nonce leak)
• Tests reviewed (coverage, legitimacy)

[OEvgeny]

Please check with links in markdown. You may want to style the links in MCS/Fluent fashion for the Fluent part.

[compulim]

Discussing offline if we should allow C2 to regret their like/dislike, and if we allow regret, what is a proper regret UX.

Recording.2025-04-29.151601.mp4

[OEvgeny]

@compulim this seems incorrect. I pushed to see if this is the issue.

[compulim]

@OEvgeny are you okay with this PR? I am okay.