fix(core): fix useYarn logic in getLockFileName (See issues-95)

[YenHub]

Hey @bahmutov

I believe this PR should address the issue highlighted in #95

I have moved the logic which sets yarnFilename, and in turn useYarn.

It now passes this value into the early return if usePackageLock is false.

Is this the correct approach to handle the issue?

Hope this helps!

Thanks

YenHub :o)

[bahmutov]

Makes sense, thank you for opening a pull request. To really lose the issue, I believe we would need an example with its own github workflow

[github-actions]

🎉 This PR is included in version 1.7.8 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀