feat: PRT - adding stickiness header

[Yaroms]

Description

Closes: #XXXX

---

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

• read the contribution guide
• included the correct type prefix in the PR title, you can find examples of the prefixes below:
• confirmed ! in the type prefix if API or client breaking change
• targeted the main branch
• provided a link to the relevant issue or specification
• reviewed "Files changed" and left comments if necessary
• included the necessary unit and integration tests
• updated the relevant documentation or specification, including comments for documenting Go code
• confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

• confirmed the correct type prefix in the PR title
• confirmed all author checklist items have been addressed
• reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

[github-actions]

Test Results

2 519 tests  ±0   2 518 ✅ ±0   27m 44s ⏱️ + 2m 8s
  124 suites ±0       1 💤 ±0 
    7 files   ±0       0 ❌ ±0 

Results for commit 7177244. ± Comparison against base commit 6088bbb.

♻️ This comment has been updated with latest results.

[ranlavanet]

if we break stickiness we want to alert the user somehow? maybe returning a header of stickiness kept / broken ?

Also will be easier to debug if users complain.

you can do this by adding a method to csm to return sticky session supposed provider and cross validating it with the provider address that returned the request in rpcconsumer_server.go