Morph key lookup issue

[joshhanley]

This PR fixes an issue with morph, where if the key already exists in the DOM and is to be moved up during morph, it wasn't getting moved correctly.

The reason was, that fromKeyDomNodeMap was empty, so the fromKeyNode in the below snippet was always empty, so the move "from" key was never running.

alpine/packages/morph/src/morph.js

Lines 259 to 265 in a920616

	let fromKeyNode = fromKeyDomNodeMap[toKey]
	if (fromKeyNode) {
	// Move "from" key...
	fromKeyHoldovers[fromKey] = currentFrom
	fromChildren = dom.replace(fromChildren, currentFrom, fromKeyNode)
	currentFrom = fromKeyNode

Removing the commented out keyToMap(fromChildren) got it working, but then caused an infinite loop. This was due to dom.replace() replacing the old with the new, but leaving the new one in its place in the array, causing two references to the dom node. So then when any dom.() methods run and try to find the index of the node, there would be two of them but only the first was ever returned. I opted to update dom.replace() but this could also be done in the above from key move code.

This fixes livewire/next#99

There is a failing test directives/x-bind-style.spec.js but running those tests locally they pass, so I believe it's unrelated.

Hope this helps!

[joshhanley]

Turns out the failing x-bind-style tests are due to the formatting in the test file. Someone has already submitted a PR to fix #3631