300 url safe panel paths

[jens-aggergren]

Fixes #300

Depending on the settings, the webserver might not always handle escaped forward-slashes in the way, which this plugin expects it to.

This specifically results in a 404 when trying to edit a redirect-entry, unless the AllowEncodedSlashes NoDecode is set for the Apache Server. The problem also occurs in relation to nginx.

Many hosting solutions does not allow customers to change such settings for the web-server, and so another solution is required.

Proposed Changes

• Replace forward-slash with the non-visible ascii-characer "GROUP-SEPARATOR" (Oct: 035, Dec: 29, Hex: 1D). By using a non-visible character we ensure that the id generation from redirect pattern is always unique.
• In src/panel/components/Tabs/RedirectsTab.vue, change the dialog route accordingly.
• In src/classes/Redirect.php, the value returned from the id() method is changed accordingly.

Futher remarks

This pull request includes an additional commit, which fixes a unit-test problem. This problem appears to be unrelated to the any to the changes in this pull request. The compiled index.js and index.css have also been commited

[basemod]

This fixes an issue when there is more than one slash (as in "/foo/bar") in the URL that is to be redirected.

[bogdancondorachi]

I can confirm that this solves the issue on my setup as well. Thanks @jens-aggergren

[distantnative]

Thanks a lot 🙏🙏🙏

[jens-aggergren]

Thanks a lot :pray: :pray: :pray:

You're very welcome. And thanks for making this very useful plugin in the first place.