Update navigation.yml to add EDOT Troubleshooting

[theletterf]

This adds EDOT Troubleshooting docs to the navigation.

Contributes to elastic/opentelemetry#333

+CC @alexandra5000

[theletterf]

@elastic/docs-engineering The https://github.com/elastic/docs-content/blob/main/troubleshoot/toc.yml file is composed of files exclusively. How do we determine the position of the imported troubleshooting in the nav?

[theletterf]

@colleenmcginnis @shainaraskas Do we consider Troubleshooting "narrative" docs? Is it a requirement for EDOT troubleshooting docs to live inside docs-content? Aleks and I were thinking of serving it from the opentelemetry repo, but we could move it to docs-content, too.

[shainaraskas]

@colleenmcginnis @shainaraskas Do we consider Troubleshooting "narrative" docs? Is it a requirement for EDOT troubleshooting docs to live inside docs-content? Aleks and I were thinking of serving it from the opentelemetry repo, but we could move it to docs-content, too.

I can imagine this changing long term. we had an external requirement to create a single home for the troubleshooting docs, but from a reader pov, not a writer pov.

in my experience, these are largely authored by support, which is one reason to keep them in the docs-content repo (mostly easier oversight and review cycles but that might not be worth much).

The complexity here is perhaps pivoting from the single-repo to multi-repo model (doing the original planning for this I recall was a little bit of a headache). I haven't done a lot of this myself and am not sure of what's involved. colleen might know more, dev definitely will.

[theletterf]

@shainaraskas Thanks! I think @lucabelluccini and the EDOT devs are already used to the EDOT troubleshooting docs being in the opentelemetry repo, so in this case I lean towards keeping them there.

[theletterf]

This won't work, unfortunately. We're going to move the docs to docs-content....