psh: add terminal control codes test

[maska989]

Description

JIRA: CI-397

Motivation and Context

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: armv7a7-imx6ull-evk.

Checklist:

• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing linter checks and tests passed.
• My changes generate no new compilation warnings for any of the targets.

Special treatment

• This PR needs additional PRs to work (list the PRs, preferably in merge-order).
  psh: Add fast cursor movement and cut&paste phoenix-rtos-utils#211
  armv7a9-qemu: Adjust serial device phoenix-rtos-project#997
  Using armv7a9-zynq7000-qemu startup script without qemu control #352
• I will merge this PR by myself when appropriate.

[mateusz-bloch]

I'm considering whether to organize the tests in a uniform manner, for example, in relation to the CONTROL CODE CHEAT SHEET, and whether to expand the tests from basic ones that test a given control code, to tests that use several, and up to those that use as many as possible. It would be beneficial if the combinations reflected real-world scenarios. So, then you could also divide the tests into separate functions (?)

[maska989]

This test is just to check that this control codes works, doesn't need to test them with full possibility use set.