Rethink Oracle component version mismatch exception

[nj1973]

When the software version does not match the database package version commands will not run due to this exception:

gluent.OffloadException: Mismatch between Oracle component version (6.0.7-DEV (027076c)) and binary version (6.0.8-DEV (878092c))

The database code is now much simplified and will rarely change, even more rarely will a change be a breaking change. We've seen in recent customer engagements that getting access to a privileged database account is often difficult and time consuming.

Thoughts:

1. Ideally we would change the logic behind this message to be based on a repo version. We only advance the repo version for breaking changes and let customers overlay GOE software without running the database upgrade script in most cases
2. If that is going to take too long we could look to downgrade the exception to a warning and create another issue for 1 above
3. Or we could leave the exception in place but downgrade to a warning if in force mode