ansible-runner: guidance requested on possible Apache-2.0/GPL-3.0 incompatibility

Hello

While reviewing ansible-runner for the new version I noticed that the 
file src/ansible_runner/display_callback/callback/awx_display.py and the 
directory 
test/fixtures/projects/collection_role/collections/ansible_collections/groovy 
are licensed under GPL-3.0-or-later, while the project is licensed with 
Apache-2.0.

These files were therefore removed from the source package. However this 
breaks the package and I forwarded the bug them to consider to 
re-license [1]. The upstream already consulted internally and responded 
that there is no licensing incompatibility problem [2].

Their argument is that the GPL file in question is not actually used by 
the project code. According to them this means the file is a "aggregate" 
under GPLv3, and that distributing it alongside Apache-2.0 code in the 
same repository is fine.

Would it be acceptable for Debian to ship these GPL-3.0-or-later files 
inside an otherwise Apache-2.0 project if they are not used by the main 
code? Can this be considered a aggregation when everything is 
distributed in the same source package and in binary package?

Any guidance would be appreciated.

[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1130233
[2] 
https://github.com/ansible/ansible-runner/issues/1217#issuecomment-1505601824

Thank you and cheers
Saki