Modify partition-level primary tracking to only markdown on success or non-transient error with hub region header

[jeet1995]

Summary

Modify partition-level primary tracking orchestrated through reads to only markdown when reads return success or non-transient error code, with hub region processing header pinned for these reads.

Details

• Update the partition-level primary tracking logic to restrict markdown triggers:
  • Only markdown when the read returns a success status code
  • Only markdown when the read returns a non-transient error code
• Pin the hub region processing header for these reads so that the tracking is scoped to hub region responses
• Transient errors should not trigger primary tracking markdown

Motivation

Ensures partition-level primary tracking is only updated based on definitive responses (success or permanent failure), preventing incorrect tracking updates from transient errors. The hub region processing header pin ensures tracking accuracy in hub region caching scenarios.