feat: Upgrade to Foundation 6.6

[hangy]

I suggest that we upgrade from Foundation 5.5.x to Foundation 6.6.x. For now, this PR is a placeholder for the migration, which still requires some additional manual adjustments.

Part of

• Keep dependancies up to date #5522
• CSS revamp

[teolemon]

Nice :-)
I was trying to use newer features of foundation, and I remembered this PR. Can't wait 👍

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[stephanegigandet]

Hi @hangy , I'm running into issues with Foundation 5.5. (I can't get dynamically created accordion to work).
Can you tell me what's missing in this PR? Maybe I can help finish it.

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities (and 0 Security Hotspots to review)
0 Code Smells

No Coverage information
0.0% Duplication

[hangy]

Can you tell me what's missing in this PR? Maybe I can help finish it.

I'm not sure what to use for the drilldown, since the original Foundation 5 component has disappeared:

Also, the response layout looks a bit weird:

Apart from that, I think it's mostly minor UI nitpicks, unless I missed major changes in master. I think the easiest way to see it yourself is to pull my farout branch and test it yourself. 🙂

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[teolemon]

@hangy : could you have a look if the rebase is doable ?
@alexgarel : if I remember well, we can do a deploy branch to push that to .net ?

[hangy]

@hangy : could you have a look if the rebase is doable ?
@alexgarel : if I remember well, we can do a deploy branch to push that to .net ?

I don't think so. The PR probably needs to be restarted - at least when it comes to the HTML, there are a lot of changes, because the content was moved to template::toolkit after I started it.