Improve status messages for app bulk execute task

[nickwesselman]

WHY are these changes introduced?

To improve the formatting of app bulk execute status messaging when --watch is used.

WHAT is this pull request doing?

• Adds the type field to all bulk operation GraphQL queries and mutations
• Updates the generated TypeScript types to include the new BulkOperationType enum
• Improves the bulk operation status formatting to differentiate between query and mutation operations
• Updates status messages to be more specific about whether objects are being read (for queries) or written (for mutations)

How to test your changes?

1. Run a bulk operation query and verify that the type field is returned
2. Run a bulk operation mutation and verify that the type field is returned
3. Check that the status messages correctly show "objects read" for queries and "objects written" for mutations
4. Verify that all tests pass with the updated formatting

Measuring impact

How do we know this change was effective? Please choose one:

• n/a - this doesn't need measurement, e.g. a linting rule or a bug-fix
• Existing analytics will cater for this addition
• PR includes analytics changes to measure impact

Checklist

• I've considered possible cross-platform impacts (Mac, Linux, Windows)
• I've considered possible documentation changes

[nickwesselman]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• Improve bulk operation polling with faster initial checks and hide zero counts #6695
• Support numeric IDs in bulk operation status command #6694
• Update info banners with organization info, and add to status command #6693
• Improve status messages for app bulk execute task #6692 👈 (View in Graphite)
• Make --output-file flag dependent on --watch in bulk operations #6691
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

We detected some changes at packages/*/src and there are no updates in the .changeset.
If the changes are user-facing, run pnpm changeset add to track your changes and include them in the next release CHANGELOG.

Caution

DO NOT create changesets for features which you do not wish to be included in the public changelog of the next CLI release.

[nickwesselman]

Part of https://github.com/shop/issues-api-foundations/issues/1149

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	79.19% (-0.01% 🔻)	13902/17555
🟡	Branches	73.17% (-0% 🔻)	6792/9282
🟡	Functions	79.33%	3562/4490
🟡	Lines	79.55% (-0.01% 🔻)	13133/16510

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / ConcurrentOutput.tsx	98.36% (-1.64% 🔻)	92% (-4% 🔻)	100%	98.33% (-1.67% 🔻)

Test suite run success

3485 tests passing in 1406 suites.

Report generated by 🧪jest coverage report action from 4b2abcd