fix: types path incorrect

[curtdept]

By creating this pull request you agree to the terms in CONTRIBUTING.md.
https://github.com/Infineon/.github/blob/master/CONTRIBUTING.md
--- DO NOT DELETE ANYTHING ABOVE THIS LINE ---

CONTRIBUTING.md also tells you what to expect in the PR process.

Description
Typescript was not correctly resolving types. After investigation, types path is incorrect due to changes with bundle directory structure.

[curtdept]

@tishoyanchev @verena-ifx

[verena-ifx]

@curtdept Thanks! I will test this, as what solved it for us now, was using vite as a build-tool inside the React app instead of React-scripts.

[tishoyanchev]

Opened a new issue: #1472

[verena-ifx]

@curtdept unfortunately, changing the types path still does not make the react wrappers work when used inside a react app that was created using react-scripts.

[curtdept]

@verena-ifx it was working well for me, however, these newest builds are missing the types completely now :| And are complaining of a missing dependency @stencil/react-output-target

This is 25.1.0

and this is 24.6.4 (the last good we have been able to use)

Freshly made 26 canary (no types)

Which is odd because if I build it locally, the stuff is there... this is after
build:components
build:components-react

This line in your tsconfig is also preventing you from detecting this error.
"noImplicitAny": false,

Its treating all missing type definitions as an any type and this like says do not enforce the any type rule.
https://www.typescriptlang.org/tsconfig/#noImplicitAny