Replace useChromium with equoChromium

[nedtwigg]

@agustinschilling Just wanted to let you know about this PR since it changes some stuff from your original PR

• Add Equo Chromium implementation in equo ide #123

From a user perspective the only change is that it deprecates useChromium to replace with equoChromium (which is the name you originally proposed in your PR).

From a dev perspective, the big change from an earlier PR is that the plugin catalog can now handle pure-maven plugins, not only p2 plugins. So instead of EquoChromium being a "magic value" implementation of IdeHook, it can be a plain catalog entry.

The point of this change is that now equoChromium can be a dependency in the catalog entries. For example, pde requires jdt. We are about to launch a ChatGPT plugin in the catalog, and now it can use equoChromium as a catalog dependency. There's also less special-casing.

[nedtwigg]

@agustinschilling a question for you: is there a changelog somewhere for the GPL version of Equo Chromium? I see we've been on 106.0.3, and I just brute-force searched with manual URLs to discover that 106.0.9 is now available. It would be good to know what is better about .9 than .3

e46105b

[agustinschilling]

Hi @nedtwigg !,

You're right, we don't have a changelog for the GPL version yet. We are working on a solution. In the meantime, you can check the changes made in the last released version of Chromium v106, by visiting this link:

https://docs.equo.dev/chromium/106.x/reference/release-notes.html

Although it is not specifically for the GPL version, it will give you a good idea of what was updated in the latest version.