V19 updates

[damyanpetev]

State based on #749, will switch to vnext target once that's merged.

Generated package updates from IgniteUI/igniteui-xplat-examples#830:

• chore: sync chart toolbar data-grids module ref - from IgniteUI/igniteui-xplat-examples@e09b94d
• chore: sync samples grids packages deps, add data-grids - from IgniteUI/igniteui-xplat-examples@d4fc56b
• chore: sync update react template to 19 alpha packages - from IgniteUI/igniteui-xplat-examples@6435e0d

---

igniteui-react-grids and igniteui-react Breaking changes:

This release include a major rework of some of our React components internals leading to the following changes:

• Now using React function components, therefore refs obtained from a component will be a forward of the native element instead of a class component instance. Since those are custom elements with mostly the same component-specific API, in addition to the DOM APIs without the need to additionally access native element, that means many of the uses could remain unchanged but there are possible changes required - such as not needing an extra property to access the DOM element.
• Componenets no longer accept alternative string union on all prop types (e.g boolean | string or number | string). Additionally, string union types (enum-like) are no longer case-insensitive.
• Componenets no longer have non-functional name prop by default. The name prop only remains in igniteui-react components, mostly form inputs such as IgrInput or IgrCombo, where it has native functionality.
• Component events are now on- prefixed.
  For example, Grid's rendered={handler} becomes onRendered={handler}
• Component events emit a single standard CustomEvent argument instead of the 'sender' as first argument. Therefore, custom props like args.nativeElement are no longer available, but native event props all are. Types for event args are available as aliases for the specific custom event, so usage accessing detail will remain much the same:
  For example:
  public handleChange(sender: IgrRadio, evt: IgrRadioChangeEventArgs) { }
  becomes:
  public handleChange(evt: IgrRadioChangeEventArgs) { } which is equivalent to public handleChange(evt: CustomEvent<IgrRadioChangeEventArgsDetail>) { }
  With the new handler signature evt.detail should be mostly the same and evt.target should is the DOM element equivalent of the sender.
• IgrButton clicked is removed, use the native onClick instead.
• IgrInput inputOcurred is renamed to onInput similar to native event.

[mddifilippo89]

@damyanpetev
can you update this with vnext once more and let me know if you want this merged before or after my pr
#750

[damyanpetev]

@damyanpetev can you update this with vnext once more and let me know if you want this merged before or after my pr #750

@mddifilippo89 Um, nether actually, I think :) There's a patch update underway and while this is the v19 update feature branch, currently it only contains the package update and none of the actual changes required (like #752, #753, #754 and more inc) to stabilize it. So it's not ready just yet, thus the Draft status.

As we discussed, I believe I've updated all samples, including the ones in your PR, so this should already contain most/all of your changes. You can try to re-target your PR to this branch to verify.

draft