tech(fmt): use wasm logging

[Druue]

Currently, we can only actively log in language-tools on the typescript side. When it comes to rust engines, we're pretty blind outside of some panic info and knowing which endpoint we're calling:

console.log('running lint() from prisma-schema-wasm')

This PR adds the feature and hook for our previously unused dep wasm-logger. Which means we can now see logs (note: not using dbg!) from prisma-fmt in the extension debug environment.

Example:

pub(crate) fn run(schema: SchemaFileInput) -> String {
    let schema = match schema {
        SchemaFileInput::Single(file) => psl::validate(file.into()),
        SchemaFileInput::Multiple(files) => {
            log::debug!("{:?}", files);
            psl::validate_multi_file(&files)
        }
    };
    ...

running lint() from prisma-schema-wasm
%cDEBUG%c prisma-fmt/src/lint.rs:18%c [("file:///Users/soph/src/prisma_debug/prisma/schema.prisma", SourceFile { contents: Allocated("generator client ") })]

closes prisma/language-tools#1193

[github-actions]

WASM Query Engine file Size

Engine	This PR	Base branch	Diff
Postgres	2.043MiB	2.043MiB	0.000B
Postgres (gzip)	813.867KiB	813.866KiB	1.000B
Mysql	2.013MiB	2.013MiB	0.000B
Mysql (gzip)	800.252KiB	800.251KiB	1.000B
Sqlite	1.914MiB	1.914MiB	0.000B
Sqlite (gzip)	762.106KiB	762.104KiB	2.000B

[codspeed-hq]

CodSpeed Performance Report

Merging #4919 will not alter performance

_{Comparing tech/wasm-logger (f6b3a3b) with main (03f1367)}

Summary

✅ 11 untouched benchmarks

[Jolg42]

This is great!