SQLite backed cache: Support sorting mgmt clusters on value in a specific condition

[ericpromislow]

Supports the UI to display managed clusters in a "saner" way.

Sample URL:

$ curl -sk https://localhost:5111/v1/management.cattle.io.clusters?sort=-spec.internal,-status.connected,spec.displayName' | jq '.data[] | [.metadata.name, .spec.internal, .status.connected, .spec.displayName]' 
[ "local", true, true,   "local" ]
[ "c-m-qc5fl797", false, true, "eptest-20250113a" ]
[ "c-m-kkjfv6r2",  false,  true,  "eptest-20250113e" ]
[ "c-m-7rp8c77v",  false,   false,  "eptest-20250113b2" ]

This sort order puts the internal clusters first, then ready (secondarily sorting by the cluster's friendly name), then the
non-ready ones.

Note putting a hyphen before boolean fields does a reverse (or DESC) sort, so the true ones appear before the false ones.

Related to #48092

Depends on:
#122 - Only because lasso is doing some sql code-generation that steve should be doing.

[moio]

Thanks @ericpromislow, this looks good to undraft to me.

As a side note, I see there are three concerns being addressed in this PR:

• adding support for an arbitrary number of sort conditions
• adding support for fields containing a dot
• adding a transformation to the v3 cluster object in order to contain a virtual .connected field in its status

I understand the reasoning behind keeping all of these in one PR, as the end-user concern/ask is actually unique. OTOH, an argument could be made to to split the change into three PRs addressing one concern each, especially because the first two affect non-Vai use cases too.

I will leave it the Frameworks team to make that decision.

From my perspective, most things look good - apart from suggestions there is only a couple of questions that are hopefully quick to settle.

Thanks!

[moio]

Looks good from my perspective once the README fully reflects the syntax change introduced.

I guess it can be merged as soon as @tomleb also approves.

Thanks for this contribution!