make more systematic use of hover view (infos, cutoffs, previews etc.)

this is another of those 'bundled' FRs that rather deal with UI principles and not neccessarily with the nittygritty of one particular function only.

I am coming here from a specific friction / block I encounter: there seems no good way to represent multiline property fields in card views, as they are 'translated' into a cut-off one liner that often gives away nothing, and serves no helpful purpose.

I would love Capacities going back to 'the old days' and allowing for at least something like a 'tool tip'-like hover info that lets one read the full property text w/o need to open the object and search the field…

… having said that, I think there are a number of areas in Capacities which could benefit from hover-views, and make more accessible the info-depth and concentration that Capacities fundamentally allows and invites so nicely.

I am thinking of other tickets here like:

https://capacities.io/feedback/p/hover-for-full-title-when-titles-are-clipped

https://capacities.io/feedback/p/show-page-preview-on-hover

https://capacities.io/feedback/p/link-preview-on-hover-and-potentially-new-basic-object-type-called-glossary-or-l

https://capacities.io/feedback/p/peek-windows-hover-on-link-to-quick-view-instead-of-half-window

https://capacities.io/feedback/p/images-20-improvements-to-the-image-object-type (-> floating image captions)

I am sure with a more systematic eye one can spot many more opportunities to make hover useful in opening up Capacities even better.

It can also be extended as logic to ideas like 'scrubbing' multiple images instead of a static cover image etc etc.