Description
We were creating a ResolvedImportBundle that didn't include existing resolvers.

The second parameter name in ResolvedImportBundle is newResolvers, which I had previously interpreted to mean any resolvers not already in the list of the resolvers. But Scala Lists are by default immutable, so I came to realize that
they wanted a new complete list of resolvers.

The :+ operand creates a new list from an existing list and an item.

Having all resolvers present makes it work; I don't exactly understand how Cromwell knows which of the resolvers to use, but it makes sense given the list is being passed around.

Tested manually using instructions in the GitHub issue. There should ideally still be a test for this. Denis added a test.

Review Instructions
Follow the instructions in #6061.

Issue
#6061
DOCK-2609

Security and Privacy

None

Please make sure that you've checked the following before submitting your pull request. Thanks!

• Check that you pass the basic style checks and unit tests by running mvn clean install
• Ensure that the PR targets the correct branch. Check the milestone or fix version of the ticket.
• Follow the existing JPA patterns for queries, using named parameters, to avoid SQL injection
• If you are changing dependencies, check the Snyk status check or the dashboard to ensure you are not introducing new high/critical vulnerabilities
• Assume that inputs to the API can be malicious, and sanitize and/or check for Denial of Service type values, e.g., massive sizes
• Do not serve user-uploaded binary images through the Dockstore API
• Ensure that endpoints that only allow privileged access enforce that with the @RolesAllowed annotation
• Do not create cookies, although this may change in the future
• If this PR is for a user-facing feature, create and link a documentation ticket for this feature (usually in the same milestone as the linked issue). Style points if you create a documentation PR directly and link that instead.