Align types for observability side navigation registration

[smith]

When registering deep links for an application (to be shown in the global side nav and to show up in global search) using ApplicationSetup.register, the deepLinks are of type AppDeepLink which takes id, title, order, path, and navLinkStatus, among other properties.

When registering sections to be shown in the Observability-specific navigation using navigationRegistry.registerSections the section entries are of type NavigationEntry, which takes label, app, path, among other properties.

If you're registering the same items as deep links are your are navigation sections, it's a bit tedious to convert title to label, etc.

There could be cases where you want different things for deep links and navigation sections, so it may not make sense for these to all be one method call, but we could better align the types to make it easier to share the definitions.