I think this is not possible because it only depends on version codes, the highest will be installed:
Alpha testing group users are eligible for the alpha, beta, or
production version of your app (with the highest version code that's
compatible with their device). Beta testing group users are only
eligible for the beta or production version of your app (with the
highest version code that's compatible with their device).
This means your alpha APKs should have the highest version codes,
followed by beta, and finally production.
If a beta APK is uploaded with a higher version code than an alpha
APK, alpha users who can install both will install the beta APK
instead of the alpha APK.
If a production APK is uploaded with a
higher version code than an alpha or beta APK, some or all of your
alpha and beta users will install the production APK, instead of APKs
of the testing tracks.
I thought that perhaps using Beta and Alpha channels but I found this answer:
Another difference is that alpha test APK's version code should be
higher than beta test one. If you upload a higher version of APK on beta
test channel, alpha test will automatically be closed. (This principle
applies for production APK too. APK version code should be 'Production
< Beta < Alpha'.)
Adding the same tester to Beta and Alpha and trying something like this:
Prod version with same code than Beta and version code 10
Beta version with same code than Prod and version code 11
The tester can install Beta version.
Upload Alpha version with code under test and version code 12
The tester can update to Alpha version and test migration.
If all correct, upload Prod version with tested code and version code 13
And upload Beta version with same code than Prod and version code 14
The tester can install Beta version.
Add feature to test and upload Alpha version with version code 15
The tester can update to Alpha version and test migration.
...