chore: use lodash-es over per-function packages

[sethidden]

lodash per-function packages are discouraged in the lodash docs (see M2-720 description for more details).

eg. lodash.debounce was last updated 6 years ago, yet lodash-es's repo has changed to debounce 3 years ago, so the per-package modules are not updated

In case you're worried this will increase the bundle size since there's one big package rather than 3 small ones - the difference between the lodash-es and lodash package on NPM is that lodash-es is published as an ES module, so doing things like

import _ from 'lodash-es'
_.debounce(() => {})

will put only files related to debounce into the bundle, not whole lodash (if you wrote from 'lodash' though, it'd import it all)

The main bundle generated in this PR is 500 bytes heavier than develop, but avoids the pitfalls mentioned in M2-720 lodash docs link

[sethidden]

I also messed with the terser in yarn.lock a bit - hopefully now yarn add works fine without the need for the lerna trick. I welcome you to checkout this branch and see for yourself if eg. yarn add is-odd (example package name) works (please run yarn before yarn add if something doesn't work)