[Discussion/Question]: How to deal with indirect dependencies that are not on CRAN

### What is your question?

### Example

Context:

- `pkg.a` depends on `pkg.b` but not on `pkg.c`.
- `pkg.c` is not defined on DESCRIPTION file of `pkg.a`
- `pkg.c` is only released on GitHub / R-Universe

For an actual case, `pkg.a is teal.modules.clinical`, `pkg.b is teal.slice` and `pkg.c is teal.data`

### Outcome

- ❌ Check fails as it cannot find an install candidate for `pkg.c`

### Solutions

1. Add entry for `Config/Needs/verdepcheck` of `pkg.a` to serve as hint on where to find `pkg.c`
- Right now it discards any entry that is not on `Depends/Imports/Suggests`
- We could use optional flag to enable this behavior
4. Re-add `Remotes` section to insightsengineering packages
- Needs research how to mitigate issue with R-Universe
5. Wait until `pkg.c` is released on CRAN
- `teal.data` should be released in next few months

### Code of Conduct

- [X] I agree to follow this project's Code of Conduct.

### Contribution Guidelines

- [X] I agree to follow this project's Contribution Guidelines.