[LogStreaming] yarn dev --logs

[mssalemi]

WHY are these changes introduced?

Fixes #0000

WHAT is this pull request doing?

How to test your changes?

Post-release steps

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
• I've made sure that any changes to dev or deploy have been reflected in the internal flowchart.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	71.5% (-0.4% 🔻)	6973/9752
🟡	Branches	68.51% (-0.24% 🔻)	3427/5002
🟡	Functions	70.98% (-0.33% 🔻)	1861/2622
🟡	Lines	72.77% (-0.46% 🔻)	6573/9033

Show new covered files 🐣

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / fetch_app_logs.ts	8.33%	0%	0%	8.33%
🔴	... / output.ts	13.64%	0%	0%	13.64%
🔴	... / subscribe_app_logs.ts	33.33%	100%	0%	33.33%
🔴	... / write_app_logs.ts	33.33%	100%	0%	33.33%
🔴	... / app-logs-process.ts	8.33%	0%	0%	8.33%

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🟢	... / app_config_webhook.ts	91.3% (-8.7% 🔻)	81.82% (-18.18% 🔻)	100%	90.91% (-9.09% 🔻)
🟢	... / setup-dev-processes.ts	95% (+0.13% 🔼)	66.67% (-1.52% 🔻)	90%	94.29% (+0.17% 🔼)
🟡	... / session.ts	76.47%	62.67% (-0.15% 🔻)	90%	76.72%
🟢	... / spin.ts	97.5%	65.38% (-3.85% 🔻)	100%	97.44%

Test suite run success

1637 tests passing in 763 suites.

Report generated by 🧪jest coverage report action from 8ead06a