o.c.opibuilder: Cleanup of OPIView instance and memento handling

A "restored" view reloads the original *.opi from memento.
But a newly opened view can re-use a previous secondary ID, receiving
that same memento, loading the old *.opi plus then the desired one.
If one *.opi is based on http://..., it will load in Job, ending up
merged with the other one.
o.c.opibuilder: Update versions.


For example main.opi, allow some headroom, accepting any runtime up to
4.0.999 as compatible
Update feature.xml
Update pom.xml
Merge pull request #743 from ControlSystemStudio/bug735

Fix opi-in-view resulting in strange mix-in of previously running *.opi