Avoid duplicate Platform initializer in generated JavaScript

[derrickbeining]

Summary

• Rename Lamdera's replacement Platform initializer to _Platform_initialize_Lamdera before kernel chunks are emitted.
• Rewrite Lamdera replacement Browser/Debugger/Platform call sites to use that Lamdera-specific initializer name.
• Keep the existing Lamdera Live HTTP kernel patch scoped to Lamdera Live builds only.

Fixes #97.

Why

lamdera make --no-wire currently emits a second global _Platform_initialize from the Lamdera replacement elm/core kernel. Downstream tooling such as elm-watch patches the standard compiler _Platform_initialize, but the later Lamdera declaration can override that patched function at runtime.

Using a Lamdera-specific initializer name preserves Lamdera's replacement runtime behavior without shadowing the compiler runtime name that downstream tools may patch.

Test plan

• Verified in a downstream Elm Land app that raw Lamdera output currently contains two _Platform_initialize definitions and that elm-watch rewrites only the first.
• Verified that renaming the Lamdera replacement initializer removes the duplicate active _Platform_initialize shape from transformed output.
• Attempted stack build --fast locally. The build did not reach this change; it failed in third-party C/native dependencies on macOS (hashable, hfsevents, entropy) against the local SDK/toolchain.

Made with Cursor

[derrickbeining]

Closing this initial compiler-side rewrite in favor of the package-replacement workflow documented in extra/readme.md. The replacement-package PRs are now open at lamdera/elm-core#1 and lamdera/elm-browser#1.