Add [inaudible] and [unclear] Tags to Improve Transcript Accuracy

[kouloumos]

Issue Description
During the review process of AI-generated transcripts, reviewers frequently encounter sections of audio that are either completely inaudible or not clear enough to transcribe accurately. To standardize the way these sections are annotated in the transcripts, we can introduce two distinct tags: [inaudible] and [unclear]. These tags will help clarify the state of the audio for anyone reviewing the transcript and ensure consistency across the review process.

Possible Solution
We can implement two new buttons in the react-markdown-editor-lite that will insert these tags directly into the editor. Here are the details for the design and functionality:

• [inaudible] Button: This button will insert the tag [inaudible] where the audio cannot be heard at all. Icon suggestion: a crossed-out speaker. Upon clicking, the corresponding tag should be inserted at the current cursor location in the editor. Example: "Here are the [inaudible] for the design".
• [unclear] Button: This button will insert the tag [unclear] where the audio is heard but not clearly understandable. Icon suggestion: a blurred sound wave or a question mark overlaying a sound wave. Upon clicking, the corresponding tag should be inserted as a suffix at the current selected word in the editor. Example: "Here are the details[unclear] for the design".

These tags can be added as extra plugins to our existing Markdown editor setup.

[aassoiants]

A low lift sol is to add that to the onboarding instructions

"If something isn't audible, you can write [inaudible]. In addition, if something is unclear, please write [unclear]."