Store the retry policy with the DurablePromise.

[avillega]

With this change we start storing the retry policy with the DurablePromise.
This enables the recovery path to use the retry policy that was set when executing the function originally instead of the default retry policy.

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 65.00000% with 14 lines in your changes missing coverage. Please review.

Project coverage is 82.70%. Comparing base (6160891) to head (4d20a70).

Files	Patch %	Lines
lib/core/retry.ts	55.55%	12 Missing ⚠️
lib/core/encoders/json.ts	75.00%	2 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #123      +/-   ##
==========================================
- Coverage   83.23%   82.70%   -0.54%     
==========================================
  Files          22       22              
  Lines        1360     1399      +39     
  Branches      337      362      +25     
==========================================
+ Hits         1132     1157      +25     
- Misses        228      242      +14     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[dfarr]

Looks good! Other than the retry policy are there any other additional options we should store in the params?

[avillega]

Looks good! Other than the retry policy are there any other additional options we should store in the params?

The only two other params that are not being store are poll (polling frequency) and the encoder. The polling frequency can be stored easily if we wanted to. The encoder might be a bit more complex, I've been thinking in the encoder a bit, and seems a bit tangled that the encoder is part of the invocation, instead of being something more global. I don't see how someone will want a different encoder for each different invocation.