Dependency Resolution doesn't happen for some jobs even after fixing the related issues

[sravankorumilli]

Describe the bug Dependency resolution only happens for the new or modified jobs. However, if there is an issue when resolving dependency for a job, it will notify the one that triggers the deployment that it is failed, but it will not be retried in the next deployment until the job is modified. The reason for failures can be the required secret is not provided, or the dependency resource does not exist. These issues can be fixed outside of this job scope, thus when it is fixed and the user attempts to redeploy, dependency resolution will not be triggered for this job as there is no modification.

To Reproduce Steps to reproduce the behavior:

1. Create a bq2bq job.
2. Make sure the job querying from the resource that Optimus does not have access to yet.
3. Run deploy command. There will be a failure when resolving dependency for this particular job.
4. Redeploy the project. Notice there is no longer issue when resolving dependency as it is not running for the job we are testing.
5. Fix the access issue.
6. Retry the deployment without making any changes to the job. Notice there is still no issue when resolving dependency as it is not running for the job we are testing. However, if it runs, it should be fixed since the access is already given.

Expected behavior Any dependency resolution issue should be retried in every deployment, regardless the job is modified or not. Or at least this issue should be shown in every deployment attempt.