Fix bug on updating status of VR & VHOR resources

[rinx]

Signed-off-by: Rintaro Okamura rintaro.okamura@gmail.com

Description:

There was a bug on updating ValdRelease & ValdHelmOperatorRelease resources by vald-helm-operator.
The cause is that there were no status field in the CRDs.
In this PR, I added status fields in the CRDs.

Related Issue:

nothing

How Has This Been Tested?:

nothing

Environment:

• Go Version: 1.15.2
• Docker Version: 19.03.8
• Kubernetes Version: 1.18.2
• NGT Version: 1.12.1

Types of changes:

• Bug fix [type/bug]
• New feature [type/feature]
• Add tests [type/test]
• Security related changes [type/security]
• Add documents [type/documentation]
• Refactoring [type/refactoring]
• Update dependencies [type/dependency]
• Update benchmarks and performances [type/bench]
• Update CI [type/ci]

Changes to Core Features:

• Have you added an explanation of what your changes do and why you'd like us to include them?
• Have you written new tests for your core changes, as applicable?
• Have you successfully ran tests with your changes locally?

Checklist:

• I have read the CONTRIBUTING document.
• I have checked open Pull Requests for the similar feature or fixes?
• I have added tests and benchmarks to cover my changes.
• I have ensured all new and existing tests passed.
• I have commented my code, particularly in hard-to-understand areas
• I have updated the documentation accordingly.

[vdaas-ci]

[CHATOPS:HELP] ChatOps commands.

• 🙆‍♀️ /approve - approve
• 💌 /changelog - add changelog comment
• 🍱 /format - format codes and add licenses
• ✅ /gen-test - generate test codes
• 🏷️ /label - add labels
• ⏪ /rebase - rebase master