fix: Improve error message on mockStep failure

[TWiStErRob]

This helps to find which mock rule is not working. If there are multiple mockSteps, it's hard to figure out otherwise which one is wrong. This helps clarify it.

Before:

Error: Could not find step
    at StepMocker.mock (.../node_modules/@kie/act-js/build/src/step-mocker/step-mocker.js:35:27)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)

After:

Error: Could not find step {"uses":"actions/upload-artifact@v4"} in job unit-test
in /foo/bar/baz/tests/repo/testRepo/.github/workflows/ci.yml

    at StepMocker.mock (/foo/bar/baz/tests/node_modules/@kie/act-js/build/src/step-mocker/step-mocker.js:37:27)
    at processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async Promise.all (index 0)

[TWiStErRob]

@shubhbapna I think my last commit solves it, can you please trigger again?

[shubhbapna]

Sorry just a nitpick but is it possible to fix the linter warning message?

[TWiStErRob]

I don't know how, it must be named mockWith otherwise the destructuring doesn't work. Can we supress for that one line?

---

Also: consider making the lint fail on warnings ;)

[shubhbapna]

You could rename the destructuring:

const { mockWith: _mockWith, ...stepQuery } = mockStep;

Or adding this line of comment directly above it should also disable it:

// eslint-disable-next-line @typescript-eslint/no-unused-vars
const { mockWith, ...stepQuery } = mockStep;

[shubhbapna]

Thank you so much!