refactor: ScanResult states

[chrisgacsal]

Description

• use CamelCase for naming

• make ScanResult states more generic and granular to be applicable for different type of assets (VM, Dir, Pod, etc)

  Old Name	New Name	Description
  INIT	Pending	Initial state for ScanResult waiting for being scheduled
  -	Scheduled	ScanResult which has been scheduled on Provider
  ATTACHED	ReadyToScan	Provider acknowledged that scan for ScanResult is ready to run
  ABORTED	Aborted	ScanResult has been aborted and the vmclarity-scanner needs to cancel all running scanners and shutdown gracefully
  IN_PROGRESS	InProgress	vmclarity-scanner is running scanners on Asset
  DONE	Done	vmclarity-scanner has finished with running all scanners on Asset
  NOT_SCANNED	NotScanned	Scanners are skipped for ScanResult

• modify ScanResultWatcher by splitting the reconcile logic to handle Pending and Scheduled states separately

• rename WaitForAttachment in vmclarity-scanner to WaitForReadyState as the corresponding ATTACHED state has been changed to ReadyToScan.

Type of Change

[ ] Bug Fix
[ ] New Feature
[ ] Breaking Change
[x] Refactor
[ ] Documentation
[ ] Other (please describe)

Checklist

• I have read the contributing guidelines
• Existing issues have been referenced (where applicable)
• I have verified this change is not present in other open pull requests
• Functionality is documented
• All code style checks pass
• New code contribution is covered by automated tests
• All new and existing tests pass