Update how to handle job_id after GitHub officially providing the feature

[kachick]

We should track this reply https://github.com/orgs/community/discussions/8945#discussioncomment-10429488

wait-other-jobs/src/report.ts

Lines 178 to 189 in 8993607

	// Ideally this logic should be...
	//
	// 1. `trigger(context).jobId === smmmary(checkRun).jobId`
	// But GitHub does not provide the jobId for each checkRun: https://github.com/orgs/community/discussions/8945
	//
	// or second place as
	// 2. `context.jobName === checkRun.jobName`
	// But GitHub does not provide the jobName for each context: https://github.com/orgs/community/discussions/16614
	//
	// On the otherhand, the conxtext.jobId will be used for the default jobName
	// Anyway, in matrix use, GitHub uses the default name for the prefix. It should be considered in list based solutions
	trigger.jobId === summary.jobName

wait-other-jobs/README.md

Lines 109 to 132 in 8993607

	If you changed job name from the default, you should set `skip-list` or roughly use `skip-same-workflow`
	```yaml
	jobs:
	your_job: # This will be used default job name if you not specify below "name" field
	name: 'Changed at here'
	runs-on: ubuntu-24.04
	steps:
	- uses: kachick/[email protected]
	with:
	skip-list: |
	[
	{
	"workflowFile": "this_file_name.yml",
	"jobName": "Changed at here"
	}
	]
	timeout-minutes: 15
	```
	Similar problems should be considered in matrix use. Because of GitHub does not provide the context.
	- https://github.com/orgs/community/discussions/8945
	- https://github.com/orgs/community/discussions/16614