disable module filtering during kickstart

I have a custom RHEL 8 ISO that is being installed via kickstart. I have a number of additional custom repositories added to the disk, including packages from CodeReady. I have one package dependency (guava-28) that i need to install, but it's being filtered out by modular filtering. Guava-28 is part of the maven:3.6 module stream only. If I enable that to get guava to install, it breaks installation of other packages that are part of the maven:3.5 stream.

I'm using: "module --name=maven --stream=3.6" to enable the module.

Is there a way during kickstart to bypass the module filtering for a single package? My only other option is to use guava20, which is part of maven:3.5 stream. However, this will require me to modify some of my source packages and i'm trying to avoid that if possible.

I know how to do this on an already installed system, but haven't found anything in the kickstart documentation that discusses ways to override the module filtering.

I'm new to modules, so i'm open to suggestions.