Make p8s an alias for pcs (escaped hex string) Fix #10058

[vicky-dx]

The p8s command was printing space-separated hex bytes, which was not intuitive. Many users expect it to print escaped hex strings like pcs does (e.g., "\x68\x65\x6c\x6c\x6f").

Changes:

• Changed p8s to call pcs internally
• Updated help message to clarify p8s is now an alias for pcs
• Provides more intuitive behavior for creating escaped strings

Before:
p8s 11 → 68 65 6c 6c 6f 20 77 6f 72 6c 64

After:
p8s 11 → "\x68\x65\x6c\x6c\x6f\x20\x77\x6f\x72\x6c\x64"

This makes p8s behave as users naturally expect when looking for escaped hex string output.

Fixes #10058

[trufae]

im pretty sure i wrote a response for this ticket but seems like i forgot to submit it..

anyway what i wanted to say is that the problem here is that we treat different command suffix in a wrong way. strings are usually determined by:

• 0 : null byte terminated
• z : zero terminated string
• s : string

it feels like p8s should be doing a string.. and this 'spaced' bytepairs seems confusing, so let me think a bit on all those subcommands a little and ill suggest more changes on the p8 subcommands as well as in px