feat: allow for setting HttpAgent ingress expiry using `ingressExpiryInMinutes` option

[krpeacock]

Description

Simply adds a configurable ingress expiry option. Includes checks against <= 0 and > 5 minutes, new errors, and e2e tests about behavior.

Important question to resolve: when the expiry is less than or equal to one minute, the tests often fail in practice due to the current "round down to the nearest minute". How should the agent handle this?

Resolution - now matches the agent-rs strategy and rounds down to the nearest second when the delta is < 90 seconds

My suggestion would be either

• disable expiry rounding if ingressExpiryInMinutes is passed
• disable expiry rounding if ingressExpiryInMinutes is passed and the value is less than 2 minutes

How Has This Been Tested?

new e2e tests and unit tests

Checklist:

• [x] My changes follow the guidelines in CONTRIBUTING.md.
• [x] The title of this PR complies with Conventional Commits.
• [x] I have edited the CHANGELOG accordingly.
• [x] I have made corresponding changes to the documentation.

[github-actions[bot]]

size-limit report 📦

Path	Size
@dfinity/agent	86.93 KB (+0.17% 🔺)
@dfinity/candid	13.58 KB (0%)
@dfinity/principal	4.97 KB (0%)
@dfinity/auth-client	61.05 KB (+0.02% 🔺)
@dfinity/assets	81.7 KB (+0.05% 🔺)
@dfinity/identity	58.18 KB (+0.03% 🔺)
@dfinity/identity-secp256k1	131.56 KB (+0.13% 🔺)

[krpeacock]

cc @robin-kunzler for prodsec review