[Linting & Validation] Error notification for inline lg should navigate to form instead of all up view

[a-b-r-o-w-n]

No description provided.

[cwhitten]

If there is an error in an .lg template, the notifications/linking heuristic should be:

• if if the error is in an inline lg template, link to the form
• if the error is a custom crafted lg template, link to the .lg file

[zhixzhan]

If there is an error in an .lg template, the notifications/linking heuristic should be:

• if if the error is in an inline lg template, link to the form

I think we can treat a template as an inline lg template if it's naming format is bfd[type]-[id]

• if the error is a custom crafted lg template, link to the .lg file

By the way, because of our inline editing experience is based on template, can lgParser diagnostic provide a property indicate error belong to which template, or a template level diagnostic ? @Danieladu @boydc2014

if not we have to repeat write code like this in several place.

// filter diagnostics belong to this template.
      lgDiagnostics = checkText(text).filter(lgDialg => {
        return (
          lgDialg.range.start.line >= template.startLineNumber &&
          lgDialg.range.end.line <= template.endLineNumber
        );
      });

[cwhitten]

addressed via #1856