Having qca2 as a separate source package would make sense, I think, as they're completely API-incompatible.
However, the maintainer would have to resolve the problem of /usr/lib/libqca.so being present in both qca-dev and libqca2-dev. Of course, it would have been better if upstream renamed the library, but it's not like that's going to happen...
