Clean up Compare, Base, and Reconciled Typed interfaces to Prevent Casting

[sandrahoang686]

Description:

We need to revisit our typing as there is a ton of casting going on that is masking our bad types. Our types should be more explicit so we dont need to cast or optionally chain as much.

Acceptance Criteria:

• Revisit Compare Types in /parcel-resolver-veda/index.d.ts
• Revisit Reconciled Types returned from useReconcileWithStacMetadata

[hanbyul-here]

Assuming this need came when we are trying to make the 'old' component ( the components that live outside of /exporation work with 'new' state management, I wonder if this will be better resolved by structuring Atoms. We are trying to reuse timelinedatasetAtoms, which is not meant to serve the other parts of the applications, and I think type mismatch happens while repurposing the timelinedatasetAtoms?

It makes sense that the types that useReconcileWithStacMetadata return might not align with our requirements elsewhere in the application. I initially thought the types defined in /parcel-resolver-veda/index.d.ts were more generalized, mainly reflecting the MDX structure. But now, I'm curious about your thoughts on how we should reshape the type. Can you detail your findings when you have a chance?

[aboydnw]

this is one of those tickets where I feel like all of the words you used are english but somehow I have no freaking clue what you said 😆