Add urldecode checkbox

[Stormtrooperroman]

Add URL Decode checkbox for the ASCII view.
This change allows toggling URL decoding for the ASCII view. Also, update the inlineAscii processing function to display UTF-8 symbols properly — for example, when the server sends escaped Unicode characters.

[peace-maker]

Thank you for your contribution! I've tried your changes and it appears to only decode some characters?

pin%5B%24ne%5D=RGFTunXA1UUrdGujlHxOIcNzTzIi4GqNVEBCIgiP
gets decoded to
pin[%24ne]=RGFTunXA1UUrdGujlHxOIcNzTzIi4GqNVEBCIgiP

So the %24 stays behind instead of showing a $.

On the other hand, this is only in the frontend so you cannot search in urldecoded data. Maybe a converter similar to the base64 one would be nice?

[peace-maker]

I guess we want decodeURIComponent?

[Stormtrooperroman]

Thank you for your reply! I will look into why it may not be working as expected. You're right, using decodeURIComponent might be a better approach.
As for implementing it on the frontend, I did so because atob doesn't support non-ASCII characters. However, with the changes in inlineAscii it might work. I'll investigate further and let you know.

[peace-maker]

We html encode all printable ascii characters. Unicode characters are inserted verbatim now which feels bad. Is there some homoglyphing possible in html? :D

Maybe html encode them too?

[peace-maker]

As for implementing it on the frontend, I did so because atob doesn't support non-ASCII characters. However, with the changes in inlineAscii it might work. I'll investigate further and let you know.

I don't think urldecoding and interpreting the resulting bytes as unicode have to be tied to one step. You can just return the "raw" urldecoded bytes?

[peace-maker]

Can you split the addition of unicode decoding into a separate pull request please? I feel this is piggy-backing on to this change and appears unrelated and worth further discussion.