output to node (Node.js) to be more runtime-agnostic

[aralroca]

Brisa was initially built with Bun, and there are Bun APIs that must continue to be used in runtime to go faster, such as Bun.serve, but we must adapt it to be more runtime-agnostic and if developers want the build can be generated and executed with Node.js. To do this it is necessary to indicate the type of output as node to apply different module resolution rules and optimizations.

Bun runtime dependencies to change to be compatible with Node:

• replace Bun.FileSystemRouter to own fileSystemRouter implementation #390
• add serve and handler to serve Node.js Brisa app #442
• replace import.meta.main from "serve" to argv to be Node.js compatible #405
• change Bun.fileURLToPath to fileURLToPath from node:url #392
• import.meta.resolveSync (deprecated) , used in getImportableFilepath, change to require.resolve #391
• replace all Bun.file to Node APIs #427
• ignore Bun.openInEditor for other runtimes than Bun (only used in dev) #436
• replace Bun.escapeHTML to own implementation #389
• replace Bun.enableANSIColors to our implementation #396
• Bun.main used in constants to know if is serve process #394
• Use Bun.hash alternative for runtime-agnostic #407
• Use Bun.nanoseconds alternative for runtime-agnostic #409
• replace Bun.env to process.env to be more runtime-agnostic #398
• do Bun.readableStreamToText on renderToString runtime-agnostic #400
• Separate "serve" and "build" processes (dev hot-reload on serve is importing the build code) #404