feat: add useDefaultSwitchClause rule

[michellocana]

Implementation of the default-case ESLint rule in Biome.

Summary

In order to migrate the project I work on from ESLint to biome, there are some rules that still need to be implemented in the Biome Linter, so I decided to give a try on the default-case rule. This is my first PR on the repository, so let me know if I'm missing something or can do something in a better way.

Test Plan

Added snapshots, for valid and invalid cases according to the default-case ESLint tests.

[codspeed-hq]

CodSpeed Performance Report

Merging #2605 will not alter performance

_{Comparing michellocana:feat/use-default-case (b7f50c8) with main (b3ed181)}

Summary

✅ 90 untouched benchmarks

[Conaclos]

Hi @michellocana. Thanks for your contribution :)

Next time, please add a comment to Linter rules from other sources to indicate your interest in implementing this rule. After some discussion, we usually open a task issue to implement the rule.

I didn't add this rule to the list of rules to implement because I thought it was unhelpful and even problematic.
It may conflict with TypeScript's completeness check.

Can you motivate why you need this rule?

[michellocana]

Hey @Conaclos, thanks for the quick review :D, and sorry, I didn't see the linked discussion before, next time I'm gonna take a look on that first.

While I completely agree that this rule becomes pretty much useless in a TypeScript environment, I found myself using this rule a lot on a plain Javascript scenario, which is the reality of some of the projects I currently work on:

const ORDER_STATUS = {
  WAITING_FOR_PAYMENT: 'WAITING_FOR_PAYMENT',
  PAID: 'PAID',
  CANCELED: 'CANCELED',
}

function getOrderLabel(status) {
  switch (status) {
    case ORDER_STATUS.WAITING_FOR_PAYMENT:
      return 'Waiting for payment.'
    case ORDER_STATUS.PAID:
      return 'Paid.'
  }
}

In the function above, getOrderLabel will return undefined if the order status is canceled or if I pass an unknown order status, and on a plain JS environment there's nothing to warn me that this code might generate a bug.

[Conaclos]

Thanks for your contribution! I think it is ready for merging :) Waiting for CI status.

[michellocana]

cool, thanks for the feedbacks, hopefully I can help more in the project ❤️