travis: Fix failing test due to change in test name

[Pearl1594]

Description

PR #5103 - https://github.com/apache/cloudstack/pull/5103/files#diff-294d96c6f789cf559c7c0b8f22ff7cb20dafba5477be4ed13ca1456c4c4e3679 renamed a test module from test_host_annotations to test_annotations leading to travis test(job 2) failure, this PR updates travis config

Failure: ImportError (No module named 'test_host_annotations') ... === TestName: Failure: | Status : EXCEPTION ===
ERROR
======================================================================
ERROR: Failure: ImportError (No module named 'test_host_annotations')
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/home/travis/.local/lib/python3.6/site-packages/nose/failure.py", line 39, in runTest
    raise self.exc_val.with_traceback(self.tb)
  File "/home/travis/.local/lib/python3.6/site-packages/nose/loader.py", line 418, in loadTestsFromName
    addr.filename, addr.module)
  File "/home/travis/.local/lib/python3.6/site-packages/nose/importer.py", line 47, in importFromPath
    return self.importFromDir(dir_path, fqname)
  File "/home/travis/.local/lib/python3.6/site-packages/nose/importer.py", line 79, in importFromDir
    fh, filename, desc = find_module(part, path)
  File "/opt/pyenv/versions/3.6/lib/python3.6/imp.py", line 297, in find_module
    raise ImportError(_ERR_MSG.format(name), name=name)
ImportError: No module named 'test_host_annotations'
-------------------- >> begin captured logging << --------------------
Failure: ImportError (No module named 'test_host_annotations'): DEBUG: ::::::::::::STARTED : TC: Failure: :::::::::::
Failure: ImportError (No module named 'test_host_annotations'): CRITICAL: EXCEPTION: Failure:: ['NoneType: None\n']

--------------------- >> end captured logging << ---------------------

Types of changes

• Breaking change (fix or feature that would cause existing functionality to change)
• New feature (non-breaking change which adds functionality)
• Bug fix (non-breaking change which fixes an issue)
• Enhancement (improves an existing feature and functionality)
• Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

[yadvr]

Checked manually, the test file doesn't exist

[yadvr]

I'm inclined to merging this as it's a very obvious fix, the file didn't exist which is replaced by file that does.