fix: handle unimplemented file capabilities slightly more gracefully

[dyc3]

Summary

The HTML language currently doesn't implement some of the file capabilities that the playground expects. This makes it so that a language does not need to implement some of these capabilities in order to work in the playground, requiring less code changes. Ideally though, we would grab the file capabilities from biome instead of try/catching. (This has been reworked to do so.)

This doesn't make HTML fully functional in the playground -- other things in biome needs to be implemented first. Once this is merged, HTML will be fully functional in the playground (for the features that are implemented)

[netlify]

✅ Deploy Preview for biomejs ready!

Name	Link
🔨 Latest commit	bae0f9b
🔍 Latest deploy log	https://app.netlify.com/sites/biomejs/deploys/66ed8299e255760008ae5e4b
😎 Deploy Preview	https://deploy-preview-1089--biomejs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[ematipico]

Ideally though, we would grab the file capabilities from biome instead of try/catching.

This is actually possible. The workspace provides a method for that

[dyc3]

Ah, then I will rework this to do that.

[dyc3]

It looks like the fileFeatures function doesn't currently indicate if the language supports parsing, control flow graph, or formatter ir.

[dyc3]

Now that the other PRs in biome are merged, everything should be good to go here.

[ematipico]

Looks good. I would use the message "Not supported" instead. The word "available" doesn't fit the case, I think. I would address @Princesseuh 's comment