Streamline Package Release, Code cleanup and Next.js Deployment related to refactoring

[hanbyul-here]

Each of the item can be a separate issue. Using this issue to collect the items.

Package Management

• Publish the package through NPM: Currently using a private registry (Verdaccio). Decide whether to continue with Verdaccio or publish to the public NPM registry. @dzole0311 via Evaluate migration from Verdaccio to public NPM registry for the veda UI #1369
• Establish a release pattern: Releases are currently ad hoc with arbitrary suffixes. Consider aligning the package release process with the current general release process or standardizing the versioning pattern.

Code Cleanup

• Ensure VEDA faux module dependency + dom router dependency doesn't exist in the library: Based on our library building result, something is still depending on VEDA faux module. (This is why the result includes various media from the stories.) Trace down where this dependency happens and remove it. It might be faster to just look up any import from 'veda' in component folder and replace it.

Type Definitions

• Export proper types, and use it from instance side: especially DatasetData and StoryData. (one gotcha: We have two DatasetData types, one exported from E&A and the other exported from VEDA - https://github.com/NASA-IMPACT/veda-ui/pull/1361/files#diff-af7791d70ec6eacf00bc029b1e7b44b287a9d2c6cc737a56acd4d1b20cda8f1cR40 It might be a good chance to clean up)

Instance optimization

• Review Next.js build configuration: Optimize the configuration for using Next.js as a Static Site Generator (SSG).
• Review subpath routing pattern: Most deployments use subpaths (e.g., /dashboard). Address asset routing issues by establishing a robust subpath handling mechanism in the Next.js instance, replacing reliance on Parcel's baseurl.