Server running in container failing with exception encountered during context initialization

[dcopestake]

Describe the bug
We're building everything using the Dockerfile from docker/server, however I noticed that the built app was failing on start-up with Exception encountered during context initialization. The errors relate to not being able to resolve certain dependencies:

 Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'workflowExecutor' defined in URL [jar:file:/app/libs/conductor-server.jar!/BOOT-INF/lib/conductor-core-3.10.7.jar!/com/netflix/conductor/core/execution/WorkflowExecutor.class]:
 Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'deciderService' defined in URL [jar:file:/app/libs/conductor-server.jar!/BOOT-INF/lib/conductor-core-3.10.7.jar!/com/netflix/conductor/core/execution/DeciderService.class]:
 Unsatisfied dependency expressed through constructor parameter 4: Error creating bean with name 'systemTaskRegistry' defined in URL [jar:file:/app/libs/conductor-server.jar!/BOOT-INF/lib/conductor-core-3.10.7.jar!/com/netflix/conductor/core/execution/tasks/SystemTaskRegistry.class]:
 Unsatisfied dependency expressed through constructor parameter 0: Error creating bean with name 'START_WORKFLOW': Resolution of declared constructors on bean Class [com.netflix.conductor.core.execution.tasks.StartWorkflow] from ClassLoader [org.springframework.boot.loader.LaunchedURLClassLoader@b81eda8] failed

I've attached a full debug log for reference as well: error.txt

Details
Conductor version: Snapshot (main at fec3116)
Persistence implementation: Postgres
Queue implementation: Postgres, Dynoqueues, SQS

To Reproduce
Steps to reproduce the behaviour:

1. Build server component from main at fec3116 using the Dockerfile from docker/server
2. Run the server using Docker image

Expected behaviour
Server starts without erroring.

Additional context
I've actually noticed what I think is the issue here. From the exception stack trace you can see that conductor-server seems to be referencing the 3.10.7 version of conductor-core. This is despite build.gradle for server referencing core as a project reference. Narrowing this down further I can see that this reference issue seems to be coming from the introduction of the orkes-conductor-queues package in 5a0dcc1, reverting this commit seems to resolve the problem and make the references correctly use the core project and product a snapshot JAR etc. I've actually reverted this commit in our fork and it's working as expected without this change.