add ioctl test

[adamdebek]

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)

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.

[nalajcie]

I've pointed out some issues which would make the code more readable ;).

[nalajcie]

pointed out some other small things to be fixed

[damianloew]

Please use the naming as it's recommended in the https://github.com/phoenix-rtos/phoenix-rtos-doc/blob/master/coding.md

[damianloew]

Two things more and I'd merge it.

[damianloew]

There is convention to name binaries using dash (test-name) as @nalajcie suggested some time ago. Now only the older tests, mainly those not supported by Unity are named with underscore. I know that it's also needed to name source file this way when using add_unity_test in Makefile, but still I'd do it this way.