fix(js): roll back module lifecycle initialization

[GrapeBaBa]

Summary

• centralize lifecycle reference release for cleanup hooks and initialization failures
• run module cleanup when export registration fails after successful initialization
• restore the environment refcount without cleanup when initialization itself fails
• add focused coverage for cleanup gating and refcount restoration

Motivation

Module initialization currently increments the shared environment refcount before invoking the addon initializer. If declaration registration, custom registration, or cleanup-hook registration then fails, the refcount is rolled back but initialized native state is left alive. A later retry can double-initialize or fail because the previous global state still exists.