API calls can be reduced by setting workflow conclusion

[sidx1024]

The workflow conclusion/status check is inside the for-loop.

Since the workflow status can is an acceptable parameter in list workflow runs API, the pagination can be reduced.

[dawidd6]

It was done like that until some weirdness with API results popped up. See #95. Maybe we could revert that now?

[KenticoDevTrev]

I ran into this where it's hitting our Artifact API call limits now... so looks like this is the culprit.

Any possibility an update can be made to use the artifact name api to simply grab the artifact by the given "name" if searchArtifacts is true?

I'm not great at Github CLI nor what you have all coded in to do a fork and pull...

[AtomicFS]

Hi, I have just started using this action in one of my projects and I am running into API rate limits all the time:

API rate limit exceeded for site ID installation

Part of the problem is that in my case there is rather significantly sized matrix, to cover multitude of use-cases. Is there any way to reduce the number of API calls? That would be wonderful and save me a lot of headache.