Disable unit tests during integration test run (SC-672)

[holmanb]

Remove unittests from integration test job in travis

Currently the integration test job executes unittests as part of package build.
The unittests have their own jobs, so this coverage is redundant and
unnecessary. Save time and remove this test.

Checklist:

• My code follows the process laid out in the documentation
• I have updated or added any unit tests accordingly
• I have updated or added any documentation accordingly

[github-actions]

Hello! Thank you for this proposed change to cloud-init. This pull request is now marked as stale as it has not seen any activity in 14 days. If no activity occurs within the next 7 days, this pull request will automatically close.

If you are waiting for code review and you are seeing this message, apologies! Please reply, tagging mitechie, and he will ensure that someone takes a look soon.

(If the pull request is closed and you would like to continue working on it, please do tag mitechie to reopen it.)

[holmanb]

This shaves about 1 minute from the longest running travis test:

Without unittests: 12m 7s
With unittests: 13m 16s (a build from a current PR that doesn't change any integration test files)

The latest commit reverted a failing unit test that was used for validating that unittests were not run during integration testing.

[TheRealFalcon]

Changes look good to me, but I'm still entirely sure all of the use cases of packages/debian and if it's appropriate to disable tests there. @blackboxsw , thoughts?

[holmanb]

@TheRealFalcon I undid changes to the debian rules file. I don't think that change actually did anything, and based on the build log output it didn't run the unit tests after undoing that change, so I don't think it was needed. Now it's gone to be safe.

For context: this skips the tests by adding DEB_BUILD_OPTIONS=nocheck env variable to the .travis.yml which causes prevents make check from running in debian/rules

[TheRealFalcon]

LGTM, thanks!