Remove conditionals that will remain fixed once 1.0.0 is released

[mvz]

Summary

Aruba contains many conditionals on Aruba::VERSION. With the pending release of 1.0.0, many of these will forever be true (or false, as the case may be). This PR removes these conditionals and any old code that will remain unused.

Motivation and Context

Part of cleaning up stuff for the 1.0.0 release.

Types of changes

• Refactoring (cleanup of codebase withouth changing any existing functionality)

[mvz]

I'll rebase this once #487 has been merged.

[maxmeyer]

Would you mind to use "feature" branches in the "aruba" repo? This might make collaborating easier. I was not aware of https://help.github.com/articles/allowing-changes-to-a-pull-request-branch-created-from-a-fork/. Would you mind, if I push to your branches as well?

[maxmeyer]

Let's remove this all together here.

[maxmeyer]

• aruba/features/04_aruba_api/command/use_last_command_stopped.feature

  Line 58 in 292ef4c

  @requires-aruba-version-1

• aruba/features/04_aruba_api/command/use_last_command_stopped.feature

  Line 71 in 292ef4c

  @requires-aruba-version-1

• aruba/features/03_testing_frameworks/cucumber/steps/command/check_output_of_command.feature

  Line 388 in 51a034a

  @requires-aruba-version-1

[mvz]

I'll fix these.

[mvz]

Fixed.

[mvz]

@maxmeyer yes, pushing to my branches is fine. I'll update my remotes anyway so I push to the cucumber/aruba repository by default.

I'm not a big fan of using / inside branch names because it interferes with command line completion and automatic local tracking branch creation.

[mvz]

I rebased but canceled the build for now due to #492.

[mvz]

@maxmeyer I made your requested changes and rebased again. Can you take another look?

[maxmeyer]

Good to go.