Fix bug in vagrant options handling

[dangoncalves]

Description

When compiling using vagrant as build environment, the first option following vagrant is skipped.

./compile.sh vagrant foo bar
In this example foo is skipped. This PR fix that bug.

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Please also note any relevant details for your test configuration.

• An image was successfully built using vagrant as builder.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published in downstream modules

[schwar3kat]

The comment in the script says '#remove "vagrant" from the command line', but the patch description has "vagrant" in the command line. './compile.sh vagrant foo bar'

[dangoncalves]

Just updated the comment. The "vagrant" is useful to enter in config-vagrant.conf. Once we are in this file, we no longer need this option.