Update Dependabot Scheduled Config

[jentfoo]

Update Dependabot with the following:

• Add jentfoo to reviewers list
• Remove crypto ignore on api (no longer using forked version)
• Add configurations for missing gomod paths

Although we are looking to explore Renovate I think we should still correct these gaps soon. As an alternative I am open to correcting these gaps with Renovate first to help validate Renovate and then just merging this for completeness after.

[rosstimothy]

Do we really need to include everything under examples? I'm a bit concerned about how many additional PRs that might produce per week.

[jentfoo]

Examples are definitely lower priority. But if we expect people to reference or start from them, it seems like we should keep them up to date. That said this PR is expanding the scope fairly dramatically, so I could be convinced to do examples as another iteration.

[wadells]

Do we really need to include everything under examples? I'm a bit concerned about how many additional PRs that might produce per week.

Some of the stuff under examples has progressed well past an example. For instance, our virtually all of internal use of teleport depends on examples/chart. We could refactor to split out the more example stuff from the production grade stuff.

[rosstimothy]

I think most users will be required to change go.mod prior to using the examples anyway since most of them depend on api and they will most definitely want to use the version of api that matches their target cluster and not whatever version we happen to have in the examples. desktop-registration only directly depends on api so I'm not sure if it will ever result in any updates.

[codingllama]

+1 for removing examples from automatic updates - I don't want to spend eng time every week touching them up.

Some of the stuff under examples has progressed well past an example. For instance, our virtually all of internal use of teleport depends on examples/chart. We could refactor to split out the more example stuff from the production grade stuff.

We should certainly do that, calling prod code "examples" is highly misleading. Who is a good person to tag for the refactor?

[codingllama]

Overall looks good, thanks Jent.

[codingllama]

Nice catch.

[jentfoo]

I have removed examples from this PR. II still do believe we need a continual update process for examples, but I don't want that to block the rest of this and I have no concerns figuring it out in another iteration.

I will try to today to get a few more PR's up to update these dependencies before the scheduled run (reduce the Dependabot qty)

[rosstimothy]

Thanks @jentfoo!

[codingllama]

I still do believe we need a continual update process for examples

I kind of disagree here, I don't think examples should create a continuous maintenance burden. It's important that they remain useful (as in they work with current Teleport), but a pre-release check could do. Touching up their dependencies, barring for CVEs, doesn't seem important.