Bug - Multiple morph calls clash

[SimoTod]

When running Alpine.morph() immediately after another Alpine.morph() call, because they are async, they run in a pseudo-concurrent way. Due to the use of global variables, the second run overrides the first one altering the result of the first morph call, see https://codepen.io/SimoTod/pen/vYpKmVZ (expecting 1-2 but getting 2-2).

To make sure that variables are not shared I moved them and most of the functions inside the morph function itself. It could probably be refactored to be a class but I didn't want to make the review more complicated so I changed as little as possible (git is already a bit rubbish at showing this kind of diff, it's probably easier to pull the file locally and compare it with the current version with a split editor).

[calebporzio]

Thanks for this @SimoTod - what you did is good as-is I think. I pulled it down to double check like you said because git's diff is garbage in this case. Thanks!