fix: handle ResourceGoneException

[omkute10]

Description

• This PR adds exception handling for ResourceGoneException within the collect_issues task in augur/tasks/github/issues.py.
• Previously, if a repository had issues disabled (returning a 410 Gone status), the ResourceGoneException would bubble up, causing the task to fail and return -1. This failure could cascade and halt other collection phases for the repository.
• The fix imports ResourceGoneException and specifically catches it during the issue collection process. It now logs an informational message and returns 0 (indicating success with 0 issues found), allowing the rest of the collection pipeline to proceed normally.

This PR fixes #3461

Notes for Reviewers

• ResourceGoneException is now imported from augur.tasks.github.util.github_data_access.
• The task now gracefully handles cases where issues are disabled or the resource is missing, treating it as a successful collection of 0 items rather than an error.

Signed commits

• [x] Yes, I signed my commits.