remove reporting pdf v1 export type

[vadimkibana]

Summary

Depends on #178281
Closes #175735

1. Removes printable_pdf from the Reporting Export Type Registry, as it has been replaced with printable_pdf_v2 in [Reporting] Create reports with full state required to generate the report #101048
2. Additional clean up of png artifacts that was missed in [Reporting] Remove PNG V1 #162517

Checklist

Delete any items that are not applicable to this PR.

• Any text added follows EUI's writing guidelines, uses sentence case text and includes i18n support
• Documentation was added for features that require explanation or tutorials
• Unit or functional tests were updated or added to match the most common scenarios
• Flaky Test Runner was used on any tests changed
• Any UI touched in this PR is usable by keyboard only (learn more about keyboard accessibility)
• Any UI touched in this PR does not create any new axe failures (run axe in browser: FF, Chrome)
• If a plugin configuration key changed, check if it needs to be allowlisted in the cloud and added to the docker list
• This renders correctly on smaller devices using a responsive layout. (You can test this in your browser)
• This was checked for cross-browser compatibility

Risk Matrix

Delete this section if it is not applicable to this PR.

Before closing this PR, invite QA, stakeholders, and other developers to identify risks that should be tested prior to the change/feature release.

When forming the risk matrix, consider some of the following examples and how they may potentially impact the change:

Risk	Probability	Severity	Mitigation/Notes
Multiple Spaces—unexpected behavior in non-default Kibana Space.	Low	High	Integration tests will verify that all features are still supported in non-default Kibana Space and when user switches between spaces.
Multiple nodes—Elasticsearch polling might have race conditions when multiple Kibana nodes are polling for the same tasks.	High	Low	Tasks are idempotent, so executing them multiple times will not result in logical error, but will degrade performance. To test for this case we add plenty of unit tests around this logic and document manual testing procedure.
Code should gracefully handle cases when feature X or plugin Y are disabled.	Medium	High	Unit tests will verify that any feature flag or plugin combination still results in our service operational.
See more potential risk examples

For maintainers

• This was checked for breaking API changes and was labeled appropriately

[vadimkibana]

/ci

[tsullivan]

/ci

[kibana-ci]

💔 Build Failed

• Buildkite Build
• Commit: d3ba4ff
• Interpreting CI Failures

Failed CI Steps

• Jest Tests #4
• Jest Tests #4
• Jest Tests #10
• Jest Tests #10
• FTR Configs #31
• FTR Configs #31
• FTR Configs #69
• FTR Configs #69

Test Failures

• [job] [logs] Jest Tests #4 / CsvGenerator Scroll strategy uses the scroll context to page all the data
• [job] [logs] Jest Tests #4 / CsvGenerator Scroll strategy uses the scroll context to page all the data
• [job] [logs] Jest Tests #10 / Handle request to generate Enqueue Job creates a report object to queue
• [job] [logs] Jest Tests #10 / Handle request to generate Enqueue Job creates a report object to queue
• [job] [logs] FTR Configs #31 / Reporting APIs Network Policy should fail job when page violates the network policy
• [job] [logs] FTR Configs #31 / Reporting APIs Network Policy should fail job when page violates the network policy
• [job] [logs] FTR Configs #69 / reporting management app Listing of Reports Paginates historical reports
• [job] [logs] FTR Configs #69 / reporting management app Listing of Reports Paginates historical reports
• [job] [logs] Jest Tests #10 / Reporting Plugin config and export types registration expect all report types to be in registry
• [job] [logs] Jest Tests #10 / Reporting Plugin config and export types registration expect all report types to be in registry
• [job] [logs] Jest Tests #10 / ReportListing flyout shows the enabled "Download" button in the actions menu for a job is done
• [job] [logs] Jest Tests #10 / ReportListing flyout shows the enabled "Download" button in the actions menu for a job is done

Metrics [docs]

Public APIs missing comments

Total count of every public API that lacks a comment. Target amount is 0. Run node scripts/build_api_docs --plugin [yourplugin] --stats comments for more detailed information.

id	before	after	diff
@kbn/reporting-export-types-csv-common	22	25	+3
@kbn/reporting-export-types-pdf	33	16	-17
@kbn/reporting-export-types-pdf-common	11	8	-3
@kbn/reporting-export-types-png-common	11	9	-2
total			-19

Async chunks

Total size of all lazy-loaded chunks that will be downloaded as the user navigates the app

id	before	after	diff
reporting	72.1KB	72.1KB	-90.0B

Page load bundle

Size of the bundles that are downloaded on every page load. Target size is below 100kb

id	before	after	diff
reporting	43.2KB	42.6KB	-644.0B

Unknown metric groups

API count

id	before	after	diff
@kbn/reporting-export-types-csv-common	25	27	+2
@kbn/reporting-export-types-pdf	34	17	-17
@kbn/reporting-export-types-pdf-common	14	11	-3
@kbn/reporting-export-types-png-common	13	11	-2
total			-20

References to deprecated APIs

id	before	after	diff
@kbn/reporting-export-types-pdf	3	0	-3
reporting	21	17	-4
total			-7

History

• 💔 Build #196587 failed 2c4cd23

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