QSvgEasingInterface hierarchy: make ctors explicit


While one could claim that the ctor arguments are each a faithful
representation of the class being constructed, and thus the ctors
should be implicit, that ignores the polymorphic nature of the
classes.

At a first approximation, all ctors (except the default ctor) of
polymorphic classes should be explicit, because polymorphy transcends
the mere encapsulation of the state passed as arguments, by adding a
behavioral dimension to the type.

As a drive-by, pass QPointF by value instead of cref, fixing a clazy
complaint.

Amends e21efa08f412753ebc9ff29f8f2c440486668138 (6.11).

Pick-to: 6.11
Change-Id: I00db017ca78ac93837236b14e05e47b07db251b1
Reviewed-by: Hatem ElKharashy <hatem.elkharashy@qt.io>
commit53b646f333ca9f0e842556b4904864bd79a55445
parent3ade2b737f0c10a3c11b4083d1c1450c4ddd8b14
authorMarc Mutz <marc.mutz@qt.io>
committerMarc Mutz <marc.mutz@qt.io>
commit timeMon, 4 May 2026 10:36:33 +0000