[EIEX-844] Use neutron kernel names in profiling table

[irtrukhina]

Summary

Replace neutron kernel kinds with names in profiling table if possible:

1. Add driver version into etdump as metadata for the last traced kernel (which corresponds to time needed for profiling info print) in runtime.
2. Check if eIQ SDK installed on host PC corresponds to the driver version from runtime.
   • If versions match -> get list of kernel names from convertor (compiler) and replace kernel numbers with kernels name.
   • If versions doen't match -> use kernel numbers in result table.

Test plan

Test included

cc @robert-kalmar @JakeStevens @digantdesai @rascani

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/21614

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❗ 1 Active SEVs

There are 1 currently active SEVs. If your PR is affected, please view them below:

• [ALERT ONLY] - System Maintenance

❌ 1 New Failure, 3 Unrelated Failures

As of commit ca86d2b with merge base 2afdd93 ():

NEW FAILURE - The following job has failed:

• pull / unittest-nxp-neutron / linux-job (gh)
  undefined reference to neutronGetSdkVersion'`

BROKEN TRUNK - The following jobs failed but were present on the merge base:

👉 Rebase onto the `viable/strict` branch to avoid these failures

• pull / unittest / macos / macos-job (gh) (trunk failure)
• pull / unittest-buck / macos / macos-job (gh) (trunk failure)
• pull / unittest-editable / macos / macos-job (gh) (trunk failure)

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[linux-foundation-easycla]

• ❌ - login: @irtrukhina / name: Irina Korchakova. The commit (ca86d2b) is not authorized under a signed CLA. Please click here to be authorized. For further assistance with EasyCLA, please visit our EasyCLA portal and chat with our support bot.

[github-actions]

This PR needs a release notes: label

If your change should be included in the release notes (i.e. would users of this library care about this change?), please use a label starting with release notes:. This helps us keep track and include your important work in the next release notes.

To add a label, you can comment to pytorchbot, for example
@pytorchbot label "release notes: none"

For more information, see
https://github.com/pytorch/pytorch/wiki/PyTorch-AutoLabel-Bot#why-categorize-for-release-notes-and-how-does-it-work.