Changed E2 spawn behavior to only run once ever

[Denneisk]

If AdvDupe2 is undefined, duped() will always run,
else, duped() will only run if the chip is not strict.

This also changes duped() and dupefinished() to be synonymous when AdvDupe2 is installed. Both will be 1 when the dupefinished() case is ran. Although it's not equivalent (because duped() is ran before constraints are created), you can now use duped() to flag both post-AdvDupe2 and regular post-dupe.

I'm not sure if this is the best solution, but AdvDupe2 is the only addon that provides a hook to run after all of pasting is finished for both the normal and alternate duplicator.

[deltamolfar]

Bit controversial, but I see more good then bad in that

[thegrb93]

Might break a lot of chips

[thegrb93]

I think the policy for compatibility breaks calls for community involvement

[Denneisk]

I'm not sure how many E2s out in the wild rely on doing something different between duped() and dupefinished(), and were made within the past 3 years, and have @strict, but I'll oblige making a community vote.

[Vurv78]

Might break a lot of chips

It seems to be @strict only? If so that's probably fine. I have made the precedent that @strict opts out of backwards compatibility, at least for things that are objectively not good.

[thegrb93]

That said... behavior differences depending on 'strict' also sounds really strange. It makes sense for 'strict' to invoke errors or warnings, but to function differently when duping is kind of uncanny.

[deltamolfar]

Well, behavioral differences is kinda already a thing with persist/global scope vars. Tho it would make more sense to have API versioning instead of strict mode, so we can forget about backwards compatibilities on major releases