refactor(one-app-runner): use semver for app version comparison

[10xLaCroixDrinker]

Description

Refactor app version comparison to use semver

Motivation

Semver is more reliable than manual comparison

Test Conditions

Refactor - existing unit tests cover the change and still pass & added new test to cover prerelease use case

Types of changes

Check boxes that apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation (adding or updating documentation)
• Dependency update
• Security update

Checklist

Check boxes that apply:

• My code follows the code style of this project.
• My change requires a change to the documentation and I have updated the documentation accordingly.
• These changes should be applied to a maintenance branch.
• I have added the Apache 2.0 license header to any new files created.

[smackfu]

There was some concern from @Matthew-Mallimo here that semver wouldn't work right if the image was just "one-app-dev:5"

#597 (comment)

[10xLaCroixDrinker]

There was some concern from @Matthew-Mallimo here that semver wouldn't work right if the image was just "one-app-dev:5"

#597 (comment)

There is unit test coverage for that use case. semver.intersects works fine for it

And as far as adding another dep, its already a dep of the bundler and I dont there are many cases of people installing the runner without that

[10xLaCroixDrinker]

I will also be adding another case of version detection required for tracing support

[Matthew-Mallimo]

Can we add a test case where the supplied docker image is just one-app:5?

[10xLaCroixDrinker]

@Matthew-Mallimo That test case already exists on line 411