fix(routing): special chars support

[wass3r]

fixes go-vela/community#487

we are very generous with what we allow for secret/schedule names. unfortunately it's possible to create resources you can't retrieve if they contain certain characters. it's also possible to create resources with certain character in its name that are retrievable, but the UI wasn't able to handle that correctly. this fixes that. there should be a follow-up fix on the API side to disallow creating resources with certain characters to avoid the scenario of un-retrievable secrets, in particular resources that are queried by name in the URI (which should be its own discussion, probably) 😞. we still need to support existing resources that were created with "creative" names to allow management (hopefully a delete?).

in summary, this PR:

• prevents user from creating resources with un-retrievable names if they contain certain characters
• fixes an issue where characters weren't encoded/decoded correctly to allow management of resources using certain characters (#, ', ?, etc) in their name

failed after merge to main

[wass3r]

@KellyMerrick looks like it was a temporary issue. i reran the failed workflow and it's good now.