cleanup console.logs and moved to proper log level console to make finding stray console.logs easier

This project does not make use of npm at all. In addition, corepack's
npm will refuse to run in a project that defines packageManager in
package.json to be yarn. If we are using standalone yarn legacy,
it will just run fine. If using corepack, it will automatically
download (if needed) and use yarn v1.

For example it would do the following:

    let subst = "d3bf557c";

Not only `err`, `stats.hasErrors` also should be handled.
I found this bug in [Pipeline 42881 build] - some errors exist,
but build result was successful.

See also: https://webpack.js.org/api/node/#error-handling

[Pipeline 42881 build]: https://git.pleroma.social/pleroma/pleroma-fe/-/jobs/225066

https://stackoverflow.com/questions/69343038/cant-import-the-named-export-xxxx-from-non-ecmascript-module-only-default-expo

polyfills also.

generated properly

This reverts merge request !856