Missing validation on missing referenced exporters, receivers, processors, extensions

[bripkens]

The pipelines may be referencing components that do not exist, and OtelBin is not raising those as issues. in the screenshot, the health_check/i_do_not_exist extension is not declared (only heath_check is), so this configuration is invalid. The same applies with, for example, a traces pipeline referencing an extension that is not declared in the extensions list.

[bripkens]

@mmanciop: This is now deployed, do you also wanna give this a test? :)

[mmanciop]

I like what the editor does, I just that the pipelines would still be visible, and the reference to the missing component would be highlighted with some question mark or so.

[roshan-gh]

@mmanciop the pipeline is still visible with warnings, but with errors it's not visible. Doesn't it make sense this way?

[mmanciop]

It depends on the nature of the error. YAML is broken -> cannot visualize. Config references some stuff that does not exist -> makes perfect sense to show from where you are referencing the stuff that does not exist, because where it is referenced from is important context to under whether you fix the config by adding the missing component, because you need it, or you delete the dangling reference.

[roshan-gh]

It makes sense, right. Then I will change the codes to have the visualization with custom errors+warnings. @mmanciop @bripkens

[roshan-gh]

Fixed it in change cursor to pipeline/definitions PR @mmanciop @bripkens

[mmanciop]

Subsumed in #94