fix: Change from IgnoreAccessDeniedServiceDisabled to IgnoreCommonErrors

[bbernays]

🎉 Thank you for making CloudQuery awesome by submitting a PR 🎉

Summary

When we use IgnoreAccessDeniedServiceDisabled we have to handle certain errors like 404/ Resource not found errors in the resolvers. By changing to IgnoreCommonErrors we get that at the table level without any extra code.

I am not 100% sure this is valid or if there are cases when we do NOT want to ignore 404s

---

Use the following steps to ensure your PR is ready to be reviewed

• Read the contribution guidelines 🧑‍🎓
• Run go fmt to format your code 🖊
• Lint your changes via golangci-lint run 🚨 (install golangci-lint here)
• Update or add tests. Learn more about testing here 🧪
• Update the docs by running go run ./docs/docs.go and committing the changes 📃
• If adding a new resource, add relevant Terraform files in a separate PR 📂
• Ensure the status checks below are successful ✅

[roneli]

LGTM

Regarding the edge cases, in general the resolver still needs to handle not founds specially in cases where its listing and doing on each on an action.

Root resolver: resolves 100 resources

• relation resolver: for each resource resolve - if not found (with new ignore error + using root table ignore error, it will just not resolve and not be inserted in DB), same with columns

On the other hand on Root Resolver if we do this logic and return on a not found we won't resolve the next 100 resources, so it should continue to resolve if it gets a not found.

[disq]

I was clear for me but now I'm all confused 😂