chore: use @std prefix for internal module specifiers

[iuioiua]

This change aims to replace all relative import specifiers targeted at tests/util/std with mapped ones (using a deno.json file). Towards updating the std git submodule.

[dsherret]

The tests sharing a config file is fine, but we should probably update the tools directory to have its own deno.json.

[dsherret]

Maybe we should add a deno.json in the tools directory that gets auto-discovered? Then we don't need to add --config here. It's also strange for these to be using something in tests/config

[iuioiua]

Nice suggestion. I didn't know deno.json auto-discovery worked like that. TIL. Can we not also add a deno.json to tests or would that interfere with the tests?

[bartlomieju]

It would most likely interfere we some of the tests - but +1 for adding another deno.json in tools/ directory

[dsherret]

In many cases we've traded a relative specifier in the code for a relative specifier when launching the command. It would be nice to have all the tests importing from the fake JSR registry instead of a shared config file like this.

[iuioiua]

What's the best way to vendor the code into tests/registry/jsr/@std?

[bartlomieju]

I think this is fine for this pass - we're still using a really old version of std, after this lands I think we should figure out a way to easily vendor 1.0 version of std from JSR and then update this file.

[bartlomieju]

LGTM, let's get deno_std submodule updated ASAP 🙏