🐛 Fix javascript enqueue handle

[Log1x]

• fix(bundle): Fix javascript enqueue handle (Fixes Bug: Javascript not executing in production build since 2.1.0 #238)
• chore(bundle): Add missing docblocks

[QWp6t]

The problem with using + instead of array_merge() when it comes to indexed arrays is that it will clobber matching indexes on the 2nd array. So we'll have to figure out a more workable solution, I think, unless entrypoints.json will NEVER have js and mjs keys at the same time. (cc @kellymears)

[kellymears]

@QWp6t If a user enables esm it likely will not emit js -- with defaults.

But there may be very good reasons to use mjs and js together, I'm really not sure. I think it's good to support mjs/js both, if possible. It would be pretty easy for users to make a couple small mods and end up in a situation where both keys are present.

[Log1x]

Adding an array_merge() to inline() in Enqueueable seems to be the easiest solution. This will keep the array keys the same during enqueueing and inlining.

[QWp6t]

LGTM 🚀