disable renovate for developer doc generators.

[mshustov]

Summary

• we have to regenerate docs on a version update. otherwise in the upcoming PR when API changed we have tons of unrelated changes in the docs Route tags #37344
• those tools are quite unstable and there are no tests in Kibana. we cannot make sure everything works properly.

Checklist

Use strikethroughs to remove checklist items you don't feel are applicable to this PR.

• [ ] This was checked for cross-browser compatibility, including a check against IE11
• [ ] Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• [ ] Documentation was added for features that require explanation or tutorials
• [ ] Unit or functional tests were updated or added to match the most common scenarios
• [ ] This was checked for keyboard-only and screenreader accessibility

For maintainers

• This was checked for breaking API changes and was labeled appropriately
• This includes a feature addition or change that requires a release note and was labeled appropriately

[elasticmachine]

Pinging @elastic/kibana-platform

[elasticmachine]

Pinging @elastic/kibana-operations

[mshustov]

btw which team is responsible for updating dependencies? how can we get the latest typescript version? the update will require some manual work
@elastic/kibana-platform @elastic/kibana-operations

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request

[spalger]

Operations is handling dependency updates by default, but any team can handle them if they like! I'll probably handle the typescript update once I've made it through the smaller, simpler updates.

[spalger]

LGTM

[elasticmachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request