Add ability to configure timeout for Scans

[ghost]

Description

Through the scan configuration a maximum number of seconds (timeoutSeconds) can be configured.

When a scan is triggered from a configuration this number of seconds will be added to the start time and saved as timeoutTime on the Scan object.

If while the Scan is running the current time exceeds the timeoutTime then the scan is automatically failed and any remaining AssetScans will be terminated.

If no timeoutTime is provided on a scan it will be automatically timed out 48 hours after the start time of the scan.

Type of Change

[ ] Bug Fix
[X] New Feature
[ ] Breaking Change
[ ] 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

[ghost]

I think we should drop the TimeoutTime logic now, its not great from an API UX perspective and StartTime + TimeoutSeconds satisfies the same flow in the code.

[chrisgacsal]

I think we should drop the TimeoutTime logic now, its not great from an API UX perspective and StartTime + TimeoutSeconds satisfies the same flow in the code.

Agreed. It felt weird to me as well. I thought that having the TimeoutTime could be helpful to have this field for API consumers so they do not need to calculate the actual timeout on their own. But doing the math on the client side should not be an issue.

[ghost]

LGTM, thanks @chrisgacsal