engine/orchestration: enable unit tests and fix errors

[weizhouapache]

Description

The unit tests in engine/orchestration module are skipped for now.

This PR enables the unit tests and fixes the errors with the unit tests.

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

Feature/Enhancement Scale

• Major
• Minor

Bug Severity

• BLOCKER
• Critical
• Major
• Minor
• Trivial

Screenshots (if appropriate):

How Has This Been Tested?

[weizhouapache]

@blueorangutan package

[blueorangutan]

@weizhouapache a Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

[blueorangutan]

Packaging result: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 5138

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
0.0% Duplication

[DaanHoogland]

code looks good

[DaanHoogland]

@weizhouapache do you feel this has been tested enough with packaging and the github actions?

[weizhouapache]

@weizhouapache do you feel this has been tested enough with packaging and the github actions?

@DaanHoogland
yeah, I think so.
unit tests might be skipped in some packaging jobs or CI checks, but most of them should build cloudstack with unit tests.

[rohityadavcloud]

Packaging has passed and the maven build Github Action, so unit tests are passing. Changes are only in unit tests so integration tests are n't required.