* First take on removing erroneous path characters

Paths should not accept trailing slashes or hashtags. This is a first attempt at nullifying those.

* Use rules to verify path before acceptance

Use Regex and rules to verify paths before acceptance

* Rules to prevent any leading or trailing slashes

* Complex slug for regex on path, but it elminates special chars

* Added yarn.lock to .gitignore

* Maybe we do want yarn.lock afterall

* Adding yarn.lock

* Move Regex pattern outside of export

facebook and linkedin icons were invalid

Fix: in group edit rules, write scripts permission and write styles permission can be configured. (#2829)

At present, the user that are not in the administrator group have no access to edit scripts and styles in page editor panel. This commit add configuration in group rule manage webpage so that users' permission on writing styles and writing scripts can be modified.

When using inline math ($e^{-x^2}$) the curly braces are interpreted as
attributes by markdown-it-attrs. Since most of the times they are not
valid attributes they simply get removed.

This patch escapes the curly braces (the default attribute delimiter),
fixing the KaTeX rendering errors.

It would be nice to simply skip that rule for `katex_inline` block types
but as far as I know markdown-it-attrs doesn't have such an option.

Fixes #1581

Fix for #2062. Using token.string only captured the character at the cursor. Now using the cursor location to determine suitable search text. Also corrected syntax issue where suggestion removed opening link parenthesis.

***NO_CI***

* Add overflow scroll to search results

All search results were not visible on desktop screens beyond the viewport height, adding overflow-y: scroll fixes this

* Update search-results.vue