fix(ENG-10904): export proper component

[adefreitas]

Summary by cubic

Fix package exports and build outputs so @stackone/hub exposes the correct React component and web component. Unblocks ENG-10904 by making the new Hub importable in the dashboard and sandbox behind the org feature flag.

• Bug Fixes

  • Point package entry to dist (main/module/types) with an exports map, and publish only dist.
  • Consolidate build artifacts to dist/index.esm.js, dist/index.js, dist/index.d.ts, and dist/webcomponent.js.
  • Mark React libs as external and inline CSS via PostCSS for consistent runtime behavior.

• Migration

  • Import React usage from the package root: import { StackOneHub } from "@stackone/hub".
  • For the web component, use: import "@stackone/hub/webcomponent" (stop importing from dist/react or dist/webcomponent paths).

[Copilot]

Pull Request Overview

This PR restructures the build output and export configuration to properly export the React component bundle. The changes simplify the distribution structure by moving from nested directories to a flat structure and updating package.json to properly expose the built components.

Key changes:

• Consolidates build outputs from nested directories (dist/react/*, dist/webcomponent/*) to flat structure (dist/index.*, dist/webcomponent.js)
• Updates package.json with proper export maps and entry points for both React component and web component usage
• Enhances build configuration with better TypeScript and PostCSS settings

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
rollup.config.mjs	Restructures build configuration to output files in flat directory structure and improves plugin configurations
package.json	Adds proper export maps, entry points, and files specification for npm package distribution

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

[nitpick] The external dependencies array should be moved to a shared constant or configuration object to avoid duplication if other bundles need the same externals. This improves maintainability when dependencies change.

[Copilot]

Using a wildcard deletion dist/* in the first bundle configuration will clean the entire dist directory, potentially removing files that other bundles in the same build process might need. Consider using more specific targets or coordinating the cleanup across all bundle configurations.

Suggested change

	del({ targets: "dist/*" }),
	del({ targets: "dist/*", runOnce: true }),