Setup Renovate

[confused-Techie]

This config comes partially from #321 and the renovate docs.

Additionally, this solution was agreed on via a Discord poll. With the one requirement that this is essentially "Read Only". That is, that renovate does not make commits automatically and introduce obscure bugs. This setup will not allow Renovate to submit any PRs or make any automatic changes.

This configuration will only display our dependencies that need updating as a pinned issue on the repo. From there, we could then selective tell Renovate to submit a PR to bump a dep, or we simply use this dashboard as a way to be aware of our dependencies that need to be updated.

I've gone ahead and tried to get this to match our use case as well as possible.

Currently there are a few major sections that will appear in the dashboard:

• The Editor Dev Dependencies
• The Editor Dependencies
• Our Core Package Syntax Theme and UI Theme Dependencies (It seemed like this would be much easier to keep in sync)
• Our Core Language Packages (Again, the same type of package seems easier to keep in sync)
• And finally a different section for each of our other packages

With this we could be much more aware of our dependencies, and this could then take on the brunt of responsibility, rather than us needing to identify outdated dependencies all on our own, and call them out in issues automatically.

Resolves #321

NOTE: Again this Renovate Setup Is READ ONLY It will not create any PRs

[confused-Techie]

Alright, and now that tests have come back:

• silicon_mac: ❌Failed - Expected, add allow-jit entitlement (fixes Apple Silicon builds) #454 required to pass
• find-and-replace: ✅ 43 failures - Expected
• settings-view: ❌2 Failures - 1 is expected, but seems impossible this PR caused it.
• symbols-view: ❌4 Failures - 2 Expected, but this is an issue we are seeing elsewhere. Ref: Decaf: autoflow ./lib #453 Decaf: autocomplete-css ./lib #452 yeet earlier this.keymaps.loadBundledKeymaps call #464
• tree-view: ✅ 2 failures - Expected

So while this PR really couldn't have introduced any bugs, I think this is a good benchmark for how our failure rate has changed since we last looked at it, and might need to be the updated expectancy rate from here on out, unless of course we are able to get these resolved.

[mauricioszabo]

@confused-Techie honestly, I vote for us to either fix the failing specs (when possible), or rewrite then into the Cypress tool (if posssible), or if everything fails, just comment them. That way, we can instead work on "if CI green, merge" process instead of having to "parse" the failures manually

[DeeDeeG]

Mostly this is a rubber stamp approval.

I am willing to just see if the renovate bot works with this config as intended. If we need to fix something after we have it up and running, having a good config merged makes that iteration easier.

Since this overall move was approved in a poll, I defer the main judgment to that decision-making process that is already completed.

So, yeah, let's go for it. 👍