Remove usage of BlueBird package from to Native Node.js Promises

[gerteck]

Please confirm that you have searched existing issues in the repo

Yes, I have searched the existing issues

Any related issues?

No response

What is the area that this feature belongs to?

No response

Is your feature request related to a problem? Please describe.

The packages/core package currently relies on bluebird for Promise functionality. This is a legacy dependency as modern Node.js environments now have robust native Promise support. Using Bluebird adds unnecessary bundle size and can cause type confusion (as Promise is shadowed).

Describe the solution you'd like

Refactor the codebase to remove the bluebird dependency and use native Promise.

Describe alternatives you've considered

In the past, native promises did not exist (pre-Node 8/10).

Additional context

Good to take a look at BlueBird's README.

https://github.com/petkaantonov/bluebird

Here is an excerpt:

⚠️Note⚠️

Please use native promises instead if at all possible. Native Promises have been stable in Node.js and browsers for around 10 years now and they have been fast for around 7. Any utility bluebird has like .map has native equivalents (like Node streams' .map).

This is a good thing, the people working on Bluebird and promises have been able to help incorporate most of the useful things from Bluebird into JavaScript itself and platforms/engines.

If there is a feature that keeps you using bluebird. Please let us know so we can try and upstream it :)

Currently - it is only recommended to use Bluebird if you need to support really old browsers or EoL Node.js or as an intermediate step to use warnings/monitoring to find bugs.

[gerteck]

At the same time, look for potential improvements in the core package.

This includes

• remove any type usage if possible.
• For example:

The parameter 'isDevMode' has type annotation 'any' but should be 'boolean' for type safety and consistency with how the parameter is used (converted to boolean with '!!' operator).