Coqide server renamed to RocqIDE server (coqidetop -> rocqidetop)

[HugoMartel]

Changed: coqide-server package name to rocqide-server, its executable from coqidetop to rocqidetop, and some leftover coq mentions in the UI and configuration files of RocqIDE.

I tried to not modify too much (e.g. coq occurences in the source code that will not appear on the UI, or OCaml module names still containing some Coq) otherwise this PR would have been a lot bigger in terms of changes.

I left some boxes unchecked since I am not aware if some software still rely directly on coqidetop, from what I 've seen this is not the case for at least VSRocq and PG ; and didn't test the GitLab CI

• Added / updated test-suite.
• Added changelog.
• Added / updated documentation.
  • Documented any new / changed user messages.

• Opened overlay pull requests.

[coqbot-app]

I am not triggering a CI run on this PR because the CI configuration has been modified. CI can be triggered manually by an authorized contributor.

[SkySkimmer]

It was deliberately not renamed for backwards compatibility, considering it's not user facing and not the recommended way to interact with rocq.

[HugoMartel]

It was deliberately not renamed for backwards compatibility, considering it's not user facing and not the recommended way to interact with rocq.

Ah I missed that fact from reading the previous renaming PRs. Since I am coming rather from the nixpkgs side of things than this side, I had the false idea that all binaries that contained coq were in fact considered "compatibility" binaries that linked to rocq equivalents (just like coq-makefile, coqtop, etc).

Would a similar coqidetop compatibility package be something of interest? (like the coq-core package in the dune definitions). I am willing to put more work in this PR or another related one if you feel that it may be worth it.

[SkySkimmer]

Renaming coqidetop doesn't really seem useful IMO.