[Bug]: Relative import path "@olli/kvdex/ext/zod" not prefixed with.... for `jsr` modules

### Problem description

It seems like the deno engine on deploy finds it hard to locate relative paths of jsr modules defined inside `imports` of deno.json that were added through `deno add`.
Full paths need to be defined as seperate entry in deno.json for it to work. See [here ](https://github.com/oliver-oloughlin/kvdex/issues/194#issuecomment-1986914154) and [here](https://github.com/waptik/weak-squirrel-86/commit/558e53ff9b77b8ad6bd690544819c4078efc2792)

### Steps to reproduce

1. Clone https://github.com/waptik/weak-squirrel-86
2. Create a new project on deno deploy and point it to the cloned repo
3. Wait for deployment to complete and voila!

### Expected behavior

Relative import for jsr modules defined in `deno.json` should work without the need to manually assign paths in `deno.json` or use the full path prefixed with `jsr:` inside codebase(eg: `jsr:@olli/kvdex/ext/zod`).
Meaning i should be able to safely use `@olli/kvdex/ext/zod`

### Environment

- Deno version: 1.41.1
- OS version: windows 11, wsl(ubuntu 22.04), Brave

### Possible solution

_No response_

### Additional context

_No response_

Reproduce the deployment using the weak-squirrel-86 repository and inspect its deno.json imports, then compare the relative @olli/kvdex/ext/zod reference with the full jsr: form described in the issue. Done means Deno Deploy resolves the configured relative import without manually adding full paths or changing the code to use jsr:.

Written by the indexing model from the issue text.