Fix escaped html characters in search result

[wxwxwxwx9]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• Others, please explain:

Resolves #1486.

Overview of changes:
Used v-html to render unescaped html characters (in place of the original mustache expression).

Anything you'd like to highlight / discuss:
NIL

Testing instructions:
npm run test

Serve the user guide and search for "include" keyword.

< and > that originally appears should now be replaced by < and > respectively, since the characters are no longer escaped.

Proposed commit message: (wrap lines at 72 characters)
Fix escaped html characters in search result.

Certain html characters are automatically escaped for
security reasons. However, it is not needed in our context
as the html is supplied by the user.

Let's prevent html characters from getting escaped so as
to render the html correctly.

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No blatantly unrelated changes
• Pinged someone for a review!

[jonahtanjz]

Thanks @wxwxwxwx9 for fixing this :) I've tested it and it seems to be working well 👍

On a separate note, since in our context usage of v-html doesn't cause any security threat, I was thinking that we should disable the eslint rule for no-v-html so that we can resolve all the eslint warnings during the ci checks but that can be a separate discussion/issue. What do you think about this?

[wxwxwxwx9]

@jonahtanjz thanks for the review!

On a separate note, since in our context usage of v-html doesn't cause any security threat, I was thinking that we should disable the eslint rule for no-v-html so that we can resolve all the eslint warnings during the ci checks but that can be a separate discussion/issue. What do you think about this?

Yup! I agree with you. We can do that in another PR :-)

[ang-zeyu]

Lgtm 👍

On a separate note, since in our context usage of v-html doesn't cause any security threat, I was thinking that we should disable the eslint rule for no-v-html so that we can resolve all the eslint warnings during the ci checks but that can be a separate discussion/issue. What do you think about this?

Yup! I agree with you. We can do that in another PR :-)

It's a good rule to have in case anything slips by, I think, even if it means spewing these out constantly.

We could deal with these carefully on a case by case basis though. (eslint-disable-next-line)