[EPM] Handle outdated package versions

[neptunian]

• when the user clicks on a package in the package list page they should be directed to the package they currently have installed and not the latest (if they have updates turned on it will be the latest)
• as part of [Ingest] Package settings page UI #60699, implement the {package} Version section of the settings page.
• update header with out of date icon

[elasticmachine]

Pinging @elastic/ingest-management (Team:Ingest Management)

[neptunian]

@hbharding Currently the list displays the latest package version information (icon and description). Its possible this information varies between versions. Are we wanting the List page to reflect the version they have installed, like the detail page? It would be odd if the icon changed from when they clicked on the package in the List page and landed on the Detail page. If so @ruflin I think we'd need an endpoint that functions like a bulk get to specify exactly what packages and versions i want.

[neptunian]

@ruflin What do you think about modifying the registry endpoint:
https://epr-staging.elastic.co/package/system/0.0.1
to respond with a field that has the latest version.
That way when they arrive at the package detail page i don't need to make another request to search for other versions to see if this is not the latest version (and notify them to update). If we plan to support installing any version with a list of all versions, then a property with an array of other (installable) versions (preferably in order) could work as well.

[ruflin]

My expectation is that /package/system/0.0.1 never is modified again after it is shipped. This means we can cache it forever. If we update it each time a new version of a package comes out, we can't. Could we use /package/system/ for this?

[jen-huang]

Closing this as #64689 is merged and follow up issue #64820 was created.