Remove `type` & `subtype` fields from `Contract` data model

[Y3drk]

Goal

Remove the type and subtype fields from the Contract type, as they are now deemed unnecessary.

For more info, see this comment from PR#133

Subtasks

• Remove subtype field from Contract type
  • Make sure this field isn't used anywhere beforehand (that's my current expectation) → if it is, try to come up with a reasonable refactor
• Remove type field from Contract type
  • Refactor ensawards.org/src/contract-pipelines/filters.ts to filter contract's based on their assigned protocol instead of type
  • Make sure that this field isn't used anywhere else and if it is, come up with a reasonable refactor

[coderabbitai]

🔗 Related PRs

#134 - fix: immediate fixes to Liquity contracts [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!