Archived shipments never get their TTL extended — silent eviction from temporary storage

[dinahmaccodes]

Tier: Medium
Description: archive_shipment (storage.rs:1545-1594) writes into env.storage().temporary() but never calls extend_ttl on the ArchivedShipment(id) key. Persistent shipment data is kept alive by extend_shipment_ttl called from ~15 sites in lib.rs; archived data has no equivalent, so delivered/cancelled shipment history will eventually be silently and permanently evicted with no restore path.
Files: contracts/shipment/src/storage.rs:1545-1594, contracts/shipment/src/lib.rs:3398-3423
Tasks:

• Extend TTL for archived shipment entries on write, and/or provide a way to refresh it on read
  Acceptance Criteria:
• Archived shipment records don't silently expire from temporary storage

[Timmmytunner]

@Timmmytunner has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I’ve reviewed the issue and have a clear understanding of the requirements. I’d be glad to take it on and contribute a reliable solution.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Timmmytunner to this issue.