feat: allow running a poller on custom thread

[tiagolobocastro]

feat: allow running a poller on custom thread

This required refactoring the selection to add for 3 options:
1. current thread
2. new thread on specified core
3. explicitly specified thread

This is useful as it allows us to run pollers on existing threads
to avoid running down the thread message pool.
Specifically for nvmx, rather than create a thread per replica,
we'd now be able to share threads on each core per replica.

---

feat(thread): expose the thread id from Thread

This is a monotonic increasing id which begins at 1 and is used
to identify threads.
This id cannot overflow... a restart would be required.

[tiagolobocastro]

@mergify backport develop

[mergify]

backport develop

✅ Backports have been created

Details

• #99 feat: allow running a poller on custom thread (backport #98) has been created for branch develop but encountered conflicts

Cherry-pick of 9664a7f has failed:

On branch mergify/bp/develop/pr-98
Your branch is ahead of 'origin/develop' by 2 commits.
  (use "git push" to publish your local commits)

You are currently cherry-picking commit 9664a7f.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Changes to be committed:
	modified:   Cargo.toml

Unmerged paths:
  (use "git add/rm <file>..." as appropriate to mark resolution)
	deleted by us:   .github/workflows/pr-code-lint.yaml

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally

[mergify]

🧪 CI Insights

Here's what we observed from your CI run for 9664a7f.

🟢 All jobs passed!

But CI Insights is watching 👀