The engine url is not checked for duplicates

[rusiaikinat]

Version: 1.1.0-rc
Build: portable

Bug Description

Creating a new BPM engine connection with a Base URL that already exists in another connection no longer triggers any duplication message. It is now possible to have two engine connections pointing to the same URL at the same time.

This is a regression: the duplication check itself used to fire (see issue #143, which asked to improve the wording of that message by naming the conflicting connection — implying the message was shown at that time). Now the check does not fire at all.

Steps To Reproduce

1. Open the BPM engines view.
2. Create a new connection with a given Base URL and save it.
3. Create another new connection, entering the same Base URL as in step 2.
4. Save.

Current Behavior

The second connection is saved successfully. No duplication message is shown. Two connections with an identical Base URL now coexist in the BPM engines list.