psh: enable test execution in new psh for imxrt117x

[mateusz-bloch]

JIRA: CI-461

Description

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)
• Chore (refactoring, style fixes, git/CI config, submodule management, no code logic changes)

How Has This Been Tested?

• Already covered by automatic testing.
• New test added: (add PR link here).
• Tested by hand on: (list targets here).

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).
• I will merge this PR by myself when appropriate.

[github-actions]

Unit Test Results

7 699 tests   - 1   6 984 ✅  - 1   39m 19s ⏱️ +34s
  435 suites  - 1     715 💤 ±0 
    1 files   ±0       0 ❌ ±0 

Results for commit a903b8a. ± Comparison against base commit 3a22101.

This pull request removes 1 test.

phoenix-rtos-tests/psh/touch ‑ armv7m7-imxrt117x-evk:phoenix-rtos-tests/psh/touch

♻️ This comment has been updated with latest results.

[damianloew]

Please add an info in commit description that it's done due to resolving #866 issue (someone when looking through commit history can think that it's some new feature)

[damianloew]

It's not a part of resolving issue - the issue has been already resolved and that's why we want to enable back this utility in tests

[damianloew]

It is enable due to resolved of the issue - that's not gramatically correct, it should be rather:
It is enabled due to the following issue resolution: ...

[damianloew]

Have you tested that on current changes it works stable?

[mateusz-bloch]

Have you tested that on current changes it works stable?

So the issue, reported in phoenix-rtos/phoenix-rtos-project#1103, still exists. To run the tests with changes, we can either disable the test or possibly try running it first. I tested with a reboot before the test, but the issue still occurs.