idea: load related issues at `n` depth

### 🆒 Your use case

When reading an issue, there is a chance that another one (potentially closed) is mentionned. It could be interesting to have access to this one also

### 🆕 The solution you'd like

When running the crawler, we could set a depth level so the crawer can fetch related issues

### 🔍 Alternatives you've considered

If you just fetch everything (open + closed) you will have everything anyway. (Might not always be the case, as a related issue could belong to an external repository)

### ℹ️ Additional info

_No response_