Ledger predicate: ConwayCommitteeHasPreviouslyResigned

[yHSJ]

Abstract

Implement predicate ConwayCommitteeHasPreviouslyResigned

Why?

Conformance

How?

Reference Implementation

Testing Strategy / Acceptance Criteria

Introduce fixtures for predicate coverage

Discussion points

No response

Dependencies & Related Tasks

No response

Checklist

• I understand that feature requests and unrefined work item should be open as GitHub Discussions instead.
• I have assigned this item to an existing milestone from the roadmap
• I have added a label capturing the impact of this item (i.e. value for users/stakeholders if successful)
• I have added a label capturing the delivery risk of this item (i.e. how likely is it that this task will succeed as planned)
• I have added a label capturing the effort of this item (i.e. how large is the task?)

[yHSJ]

This issue requires changes to the DB schema, and our internal data model.

Therefore, it and the related #920 are being put off until we finish other predicates. I have previously done some work on this and it sits, in an incomplete state, on the josh/cc-member-predicates branch.