[Fleet] update getPackageInfo to handle uploaded packages

[neptunian]

getPackageInfo is the handler for the route /api/fleet/epm/packages/{pkg}. Before this change it always reached out to the registry to get the package. For example if you uploaded a package called apache-0.1.4 and visited /api/fleet/epm/packages/apache-0.1.4 the registry package would be returned and not the one you uploaded. This updates to check the install source, if installed, and fetch from that source.

• update getPackageInfo to look at install source before looking for the package. If an uploaded package doesn't exist in memory, it will throw an error. This will be updated once the package storage is available and it would look there next before throwing an error, probably a 404.

• update the .zip and .tar.gz fixtures for apache-0.1.4 package to differentiate itself from the one in the registry to make testing easier. the description in the manifest was changed and the README.md in /docs to say "Apache Uploaded Test Integration". This is compared in an integration test and you can easily see the different when navigating to the package details in the UI

• introduces getPackageFromSource which can be updated once the package storage is available.

This change is needed for #83312 and #83311

Test:

1. Upload a package
   curl -X POST -u elastic:changeme http://localhost:5603/ssg/api/fleet/epm/packages --data-binary @dev/elastic/kibana/x-pack/test/fleet_api_integration/apis/fixtures/direct_upload_packages/apache_0.1.4.tar.gz -H 'kbn-xsrf: xyz' -H 'Content-Type: application/gzip'
2. Visit the route and see that the uploaded package information is being returned

3. Uninstall apache-0.1.4
4. Visit the route again and see the registry version is returned

[elasticmachine]

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

[jfsiii]

Yay! Thanks for adding the tests. Didn't get to run locally, but LGTM. Left some comments but nothing that can't be addressed later.

[jfsiii]

Not able to check right now, but does this not work as Omit<RegistryPackage|ArchivePackage?

[neptunian]

I'm not exactly sure why, but it breaks a type like this:
.
The error is:
Type '{ name: string; title: string; version: string; latestVersion: string; description: string; type: string; categories: never[]; requirement: { kibana: { versions: string; }; elasticsearch: { versions: string; }; }; ... 4 more ...; status: "not_installed"; }' is not assignable to type 'Installable<Pick<RegistryPackage | ArchivePackage, "name" | "version" | "release" | "description" | "type" | "icons" | "internal" | "data_streams" | ... 4 more ... | "format_version"> & PackageAdditions>'. Object literal may only specify known properties, and 'requirement' does not exist in type 'NotInstalled<Pick<RegistryPackage | ArchivePackage, "name" | "version" | "release" | "description" | "type" | "icons" | "internal" | "data_streams" | ... 4 more ... | "format_version"> & PackageAdditions>'.

[kibanamachine]

💚 Build Succeeded

• continuous-integration/kibana-ci/pull-request
• Commit: 717ac5a

Metrics [docs]

✅ unchanged

History

• 💔 Build #89230 failed 7511f99
• 💔 Build #89078 failed 6cb36aa
• 💔 Build #89067 failed f81b670

To update your PR or re-run it, just comment with:
@elasticmachine merge upstream