Fix flaky TSO test and remove notify keyword from test JCL

[t1m0thyj]

What It Does

• Fixes method that issues TSO commands to be more reliable and consistent with Zowe Node SDKs
  • Fetch startup messages after starting TSO session to suppress them from command output
  • Pass readReply=false query param on API call for sending command to TSO session
• Removes "notify" keyword from test JCL to prevent spamming test system with TSO notifications
• Fixes apt-get install failing to install libsecret package in Linux CI builds

How to Test

Review Checklist
I certify that I have:

• tested my changes
• added/updated automated tests
• updated the changelog
• followed the contribution guidelines

Additional Comments

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 81.88%. Comparing base (7d093e6) to head (52801dd).

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #386      +/-   ##
==========================================
+ Coverage   81.86%   81.88%   +0.01%     
==========================================
  Files          48       48              
  Lines        2768     2771       +3     
==========================================
+ Hits         2266     2269       +3     
  Misses        502      502              

Flag	Coverage Δ
unittests	81.88% <100.00%> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Copilot]

Pull request overview

This PR fixes a flaky TSO test by improving the reliability of TSO command execution to align with Zowe Node SDKs behavior, and removes the "notify" keyword from test JCL to prevent spamming the test system with TSO notifications.

Key Changes

• Modified TSO command issuing to fetch and suppress startup messages before executing commands
• Added read_reply parameter to the send() method to control whether to wait for TSO session replies
• Removed NOTIFY=&SYSUID from test JCL fixtures to prevent unnecessary system notifications

Reviewed changes

Copilot reviewed 8 out of 8 changed files in this pull request and generated 2 comments.

Show a summary per file

File	Description
src/zos_tso/zowe/zos_tso_for_zowe_sdk/tso.py	Enhanced issue_command method to fetch startup messages and added read_reply parameter to send() method for better control over TSO session behavior
src/zos_tso/zowe/zos_tso_for_zowe_sdk/response/tso.py	Made tsoData field optional in SendResponse to support responses without data when read_reply=False
tests/unit/test_zos_tso.py	Updated unit test mocks to reflect new TSO command flow with additional API calls for fetching startup messages
tests/integration/fixtures/sample.jcl	Removed NOTIFY=&SYSUID parameter from JCL job definition
tests/integration/fixtures/jobs.json	Removed NOTIFY=&SYSUID parameter from JCL code array
CHANGELOG.md	Documented the bug fix for TSO command output reliability issue
.github/workflows/sdk-release.yaml	Added apt-get update before package installation for better reliability
.github/workflows/sdk-build.yml	Added apt-get update before package installation for better reliability

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This method calls self.send(session_key, message).tsoData and wraps it with list(). Since tsoData field in SendResponse is now Optional[list[dict[str, Any]]] (can be None), calling list(None) will raise a TypeError if the API returns a response without tsoData. Consider handling the None case, for example: return list(self.send(session_key, message).tsoData or []).

Suggested change

	return list(self.send(session_key, message).tsoData)
	return list(self.send(session_key, message).tsoData or [])

[Copilot]

The documentation for the read_reply parameter only states "Whether to read the reply from the TSO session" which is vague. Consider expanding this to explain what happens when set to False (e.g., "When False, the command is sent without waiting for a reply, and tsoData in the response will be None").