Evaluate and add linting to detect at pull request issues in the change

[prasanth-reddy-wavemaker-com]

When contributor submits a pull request, we should automatically detect using linting potential issues with the change. The potential issues could be:

1. Linking to an image with incorrect path
2. Missing link, perhaps they forgot to specify the target hyperlink
3. When page is missing a mention of sidebar id
4. Has code but has not surrounded the code with back ticks. For example: /learn/request-response-processing-rest-services.md
5. Has HTML code that is not fenced properly leading it to be executed by browser causing nasty issues like Popup shown in OWASP page #97

check this remark-lint

[prasanth-reddy-wavemaker-com]

Instead of trying the markdown lint approach, which is proving to be tricky, we can use cypress to parse the generated HTML of a page to find:

1. java code which is not fenced.
2. Pages that don't have sidebar,
3. Page having links that are broken

However finding HTML, XML, JavaScript code that is unfenced should still be at linting phase. HTML, JS code that not fenced will become part of HTML and we will not be able to detect it using cypress test.