Use import() syntax for server build in templates

[aaronadamsCA]

I think there's a small opportunity to simplify and future-proof some Remix templates by importing the server build using a dynamic import with a const assertion.

As an example, this:

remix/templates/cloudflare/functions/[[path]].ts

Lines 1 to 8 in cc65962

	import { createPagesFunctionHandler } from "@remix-run/cloudflare-pages";
	// eslint-disable-next-line @typescript-eslint/ban-ts-comment
	// @ts-ignore - the server build file is generated by `remix vite:build`
	// eslint-disable-next-line import/no-unresolved
	import * as build from "../build/server";
	export const onRequest = createPagesFunctionHandler({ build });

Could be simplified to this:

import { createPagesFunctionHandler } from "@remix-run/cloudflare-pages";

export const onRequest = createPagesFunctionHandler({
  // eslint-disable-next-line @typescript-eslint/no-unsafe-return -- the server build file is generated by `remix vite:build`
  build: async () => import("../build/server/index.js" as const),
});

The const assertion ensures the import isn't evaluated by TypeScript or eslint-plugin-import. This should mean only one TypeScript ESLint rule needs to be disabled, and future rule changes are less likely to cause new problems.

Other templates could potentially benefit from a similar change.