feat: added yellow border color

[missingems]

No description provided.

[missingems]

Circling back to this discussion: #26 (comment)
In hindsight, I agree with you, @JacobHearst. that we should keep these dynamic types as raw strings. We can still maintain the enum, but perhaps place it inside a helper (e.g., Card+Enums). This way, we can update the helper to map to the new type if needed. And, when WotC decides to release a new type, at least we won’t fail to decode it. We could add a new case .unknown(rawValue: String) for new types we haven't implemented.

I severely underestimated the creativity from WotC.

[JacobHearst]

I severely underestimated the creativity from WotC.

So did I when I started this library 😂 . We do currently have unknown cases (with no associated value) for Card.Layout and Card.FrameEffect, I think it would be good to add the raw value in there as you suggested. It will be a breaking change though so I'd like to go through the library and see if there's any other improvements that would break API compatibility. Then we can just group them in the same major version instead of incrementing the major version twice.

As for this PR, what card adds this yellow border color? The smoke tests didn't catch this so I'd like to figure out why and hopefully remedy that

[missingems]

The new set Aetherdrift has a new yellow border type and I am getting decoding error out of it.

[JacobHearst]

Okay figured out the reason this wasn't caught. I'll get a fix onto main after I merge this PR