Create the @kbn/std package

[pgayvallet]

We are currently extracting some code from core to their own packages. Some of this code was using the src/core/utils module. In addition, some package were importing (js) utils from legacy that were moved to core and migrated to typescript, and importing core code from package creates a lot of problems.

This issue is to discuss moving all these utility functions to a new @kbn/std package to address these two issues.

see #76874 (comment) and #76397 (comment) for more context.

Does anyone see any problem, or reasons not to do so?

[elasticmachine]

Pinging @elastic/kibana-platform (Team:Platform)

[elasticmachine]

Pinging @elastic/kibana-operations (Team:Operations)

[tylersmalley]

I actually recently started working on #76518 which introduces a kbn/utils package (do not review, in process of making major changes). For the same reason that you found, we really need a place to have utilities that are used across packages and plugins. My thought is we can use kbn/utils and break things out if it makes sense.

[joshdover]

I think the modules in src/core/utils and what you're working on in #76518 are a bit different. With a few exceptions, the src/core/utils are mostly more like lodash than anything else. I wonder if we should put these truly generic utilities into something like @kbn/std as a "standard library" of sorts and leave the Kibana-specific bits in @kbn/utils.

[tylersmalley]

@joshdover I see -- Yeah, that makes sense to me.