Aws#282 This fixes bug #282

[sesmaili]

What type of PR is this? bug

Which issue does this PR fix: #282

What does this PR do / Why do we need it: It fixes bug #282

If an issue # is not available please add repro steps and logs from aws-gateway-controller showing the issue:

Testing done on this change: Yes

Automation added to e2e: N/A

Will this PR introduce any new dependencies?: No

Will this break upgrades or downgrades. Has updating a running cluster been tested?: No

Does this PR introduce any user-facing change?: No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[coveralls]

Pull Request Test Coverage Report for Build 5425788452

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 32.692%

---

Totals
Change from base Build 5415710026:	0.0%
Covered Lines:	3382
Relevant Lines:	10345

---

💛 - Coveralls

[mikhail-aws]

can you squash commits into single one please to keep git history clean?
you can do for example:

git reset --soft aws:main
git commit -m ...

[solmonk]

This type of approach looks okay for now, but in the long term, each condition type should be dealt separately, and only update the condition when the change is required. This way we can cover different types of statuses as well (addresses #277)