Update scichart-react to 2.0.0-alpha.2 (Examples + react boilerplates)

[jim-risen]

What

• Examples: switch from the vendored src/scichart-react stub to scichart-react@2.0.0-alpha.2 from npm (aliases commented out in tsconfig/webpack configs; stub kept in tree as fallback). Sandbox export now emits a real scichart-react version again.
• BoilerPlates/react-vite: scichart → 6.0.0-alpha.164, scichart-react → 2.0.0-alpha.2, copy the whole _wasm folder (with stripBase — vite-plugin-static-copy v4 preserves paths otherwise), explicit chart height (2.0 disables the aspect-ratio fallback).
• BoilerPlates/scichart-react: scichart 5.x → 6.0.0-alpha.164, scichart-react → 2.0.0-alpha.2, config= migrated to the new SciChartDeclarative component, whole-folder wasm copy, Readme restructured (initChart approach first, declarative after).
• Example fixes surfaced by the stricter 6.0 core:
  • UsingThemeManager: custom theme is now a constructed theme instance (plain object copy was mistaken for a Builder API theme definition)
  • BuilderApi/CustomTypes: static Name was a type annotation, not an assignment — custom palette provider registered under undefined
  • BuilderApi/FullChart: raw <SciChartReact> tag in the markdown description rendered as an unknown HTML element

Verified

• Examples client + server webpack builds pass; bundle confirmed to contain the npm package (stub markers absent)
• Both boilerplates build; wasm files land at output root
• chart-themes, custom-types and react-vite pages verified rendering in the browser

[codesandbox]

Review or Edit in CodeSandbox

Open the branch in Web Editor • VS Code • Insiders

Open Preview

[klishevich]

We have got two api now SciChartReact which accepts a function and SciChartDeclarative which accepts a config object. Which one we consider to be the default? I thought that config object is default, and if it is the case I would use the old name SciChartReact for the default case