We introduce the "content" package type in https://github.com/elastic/package-spec/pull/777. We need to add support for this type of package, items to check: * [x] `build` works * [x] `check`/`format`/`lint` work * [x] `create` can be used to create a new "content" package * [x] `dump` does not fail, and dumps resources if any between the supported types * [x] `edit`/`export` work with dashboards for content packages * [x] `install` works (dependant on support in Fleet) * [x] `status` works (dependant on support in package registry) * [x] `test`: * [x] `asset` works * [x] `pipeline` does nothing * [x] `policy` does nothing * [x] `static` works * [x] `system` does nothing (by now, could test something in the future with https://github.com/elastic/elastic-package/issues/1705)
We introduce the "content" package type in elastic/package-spec#777.
We need to add support for this type of package, items to check:
buildworkscheck/format/lintworkcreatecan be used to create a new "content" packagedumpdoes not fail, and dumps resources if any between the supported typesedit/exportwork with dashboards for content packagesinstallworks (dependant on support in Fleet)statusworks (dependant on support in package registry)test:assetworkspipelinedoes nothingpolicydoes nothingstaticworkssystemdoes nothing (by now, could test something in the future with Add automated tests with dashboards #1705)