libphoenix PIC: perf tests

[badochov]

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.

[github-actions]

Unit Test Results

         1 files  ±0    1 474 suites  ±0   1h 47m 17s ⏱️ - 1m 35s
18 716 tests ±0  15 593 ✔️ ±0  3 123 💤 ±0  0 ❌ ±0 
18 902 runs  ±0  15 740 ✔️ ±0  3 162 💤 ±0  0 ❌ ±0 

Results for commit e10058a. ± Comparison against base commit 35a66d7.

♻️ This comment has been updated with latest results.