test(deps): update dependency paket to v10 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
paket (source)	9.0.2 → 10.3.1

---

Release Notes

fsprojects/Paket (paket)

v10.3.1

Compare Source

• REVERT: #​4284

v10.2.1

Compare Source

• Fix NullReferenceException when doing paket.exe update by bumping Cache version - #​4315

v10.2.0

Compare Source

FIx NullReferenceException when doing paket.exe update by bumping Cache version - #​4315

v10.1.1

Compare Source

• Implemented group conditions for SDK-style projects - #​4247

v10.0.1

Compare Source

• Support for .NET 10.0 - #​4297
• Use NuGet.Configuration to get the path to the NuGet global - #​4301
• Add support for Artifactory by using the SearchQueryService as a fallback when AllVersionsAPI is not available - #​4303
• Fix script generation if package contains FSharp.Core name - #​4287
• Support for icon in paket.template - #​4280
• Reduced memory allocations in Requirements.simplify - #​4314

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[viceice]

@fpellet any idea why v10 of paket fails?

[fpellet]

@fpellet any idea why v10 of paket fails?

This is because it is based on an image with dotnet 6. For version 10 of paket, you need at least dotnet 9.
Is there a reason why we are specifically testing version 6? If not, I suggest updating and testing only the latest version of dotnet.

[viceice]

@fpellet any idea why v10 of paket fails?

This is because it is based on an image with dotnet 6. For version 10 of paket, you need at least dotnet 9.
Is there a reason why we are specifically testing version 6? If not, I suggest updating and testing only the latest version of dotnet.

🫣 ah,I didn't saw it. will refactor tests and drop eol dotnet versions soon