Resolve #548 - improperly connected activity

[craigfowler]

The activity I removed would never have been executed, because it is
not connected from either of the IfElse branches.
Since this is Elsa 1.x, I've fixed it using the cheapest/quickest possible
solution which is to just remove the misleading part of the sample.

[sfmskywalker]

Interestingly enough, this example would have worked properly in Elsa 2. In Elsa 2, the If activity always returns a "Done" outcome after either the "True" or "False" branch completes.

[craigfowler]

Sipke, did you install the time machine extension to Visual Studio?

When this codebase gets up to 88mph, you're gonna see some serious schtick 🤣

[craigfowler]

Also, hopefully now we've got a new commit in master (since I reconfigured its recognition of long-lived branches), SonarCloud will recognise master as one. That should mean that it stops failing PRs for the wrong reasons 👀

[sfmskywalker]

Ahhh that explains the failing build notifications I've been seeing (and blissfully ignoring 🙈 ).