Shorten id of WorkflowStepInput via graph_split.py

[altairwei]

I am used to using VSCode to write CWL documents and use Benten as a CWL Language Server to provide error checking for the editor. However, when I split the packed document using graph_split, I found that Benten was hinting that the id in my WorkflowStepInput was incorrect and that its id name contained an unnecessary prefix. Although I used cwltool --valid to validate the CWL document and found no problem, I wanted to correct the error that Benten was prompting, which is why I created this pull request.

[mr-c]

Thank you for this PR! Can you add a test case to confirm your change?

[altairwei]

Thank you for this PR! Can you add a test case to confirm your change?

I can give it a try. But graph_split doesn't have enough test cases, do you feel the need to add them?

[mr-c]

Thank you for this PR! Can you add a test case to confirm your change?

I can give it a try. But graph_split doesn't have enough test cases, do you feel the need to add them?

Even a single test case would be nice

[codecov]

Codecov Report

❌ Patch coverage is 81.81818% with 4 lines in your changes missing coverage. Please review.
✅ Project coverage is 23.87%. Comparing base (99f3b25) to head (6b90034).
⚠️ Report is 303 commits behind head on main.

Files with missing lines	Patch %	Lines
cwl_utils/graph_split.py	81.81%	4 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #54      +/-   ##
==========================================
+ Coverage   23.82%   23.87%   +0.05%     
==========================================
  Files          14       14              
  Lines       19277    19299      +22     
==========================================
+ Hits         4593     4608      +15     
- Misses      14684    14691       +7     

☔ 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.