Missed a use case when handling defined hour configurations

Previous defined hour fix handled the case where the defined hour was the only configuration.
However if another configuration was set as well, then two jobs were being created where the one job (based on the defined hour configuration) had no schedule set.
Jobs are now only created based on configurations that the VEEAM server supports - any other configuration is simply ignored.