Difficult to say on a general principle, as architectural consideration may vary depending on the actual use-case at hand.
But here is my personal advice, taking into account also the question above:
I would start by placing all the DMN models in a single "container" Kogito application, without caring too much of the inner folders etc. but making sure the model IDs are consistent and the system behaves as expected.
When eventually the application will start to grow in size (eg, more models) you may opt to split the Kogito application before it becomes a monolith.
And since the deployment scheme may vary "tomorrow", you will notice that handling the redirect within the Quarkus app will become superseded, as you will need to coordinate the deployments in a K8s or similar cloud management / solution ?
Hope these are helpful considerations