Switch to SimplexLab organization

[PierreQuinton]

This PR prepares for the switch to SimplexLab/torchjd.

For now, the documentation repo moves to SimplexLab/documentation which may not be optimal, we could change its name to something like TorchJD-site or such, and then the documentation is on that web site, we could then also have a SimplexLab-site for the simplexlab.org website.

TODO:

• Rename the repo to TorchJD everywhere where the repo is mentionned.
• (Prior to this) move the documentation to SimplexLab/torchjd-site

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Files with missing lines	Coverage Δ
src/torchjd/autojac/_backward.py	100.00% <ø> (ø)
src/torchjd/autojac/_mtl_backward.py	100.00% <ø> (ø)
src/torchjd/autojac/_utils.py	100.00% <ø> (ø)

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ValerianRey]

LGTM, but let's wait to have the SimplexLab logo to merge and make the transition.

Also, do you have a source confirming that the old URL will still work? For example, existing links to the source code in the documentation will still point to the old URL, so it's important that the old URL still works for quite a while. Also, the link to the source code in the paper should also still work (even if we release a v4).

[ValerianRey]

I'm also wondering whether we should rename the repo TorchJD (with some capital letters) in the process. The python package would still be torchjd, so we would have the code in TorchJD/src/torchjd. Does that sound like an improvement?

[PierreQuinton]

LGTM, but let's wait to have the SimplexLab logo to merge and make the transition.

Also, do you have a source confirming that the old URL will still work? For example, existing links to the source code in the documentation will still point to the old URL, so it's important that the old URL still works for quite a while. Also, the link to the source code in the paper should also still work (even if we release a v4).

I have no fully trusted source, I saw that some Github documentation but I think the best is to test ourselves and also it is not completely sure if there is a time limit to that or if it is simply the fact of creating a new repo with the same name that would terminate the link.

We will wait for the transition and I think that the thing we should be most careful about is transitioning the documentation (and this should be done prior to this). The reason is the setup of the DNS link to torchjd.org and such (we may have some down time which is completely okay).