Respect amount when listing releases

[bosunski]

Summary

This PR updates ListReleases to respect the amount value.

Implementation

• Before this change, ListReleases would keep looping until the EndCursor even when the amount was set to 1 and the release had already been found. I have now updated the conditional check that determines whether the loop should continue or break.
• I also think the purpose of amount might be misinterpreted as it is used as the first parameter in the GraphQL release query. This means amount is the number of releases that GitHub should return per query (more like per page). Instead, the amount is the maximum number of releases that should be returned after filtering. To correct this, I have set a fixed value of 10 for the first variable. This also now makes finding a single release faster since GitHub will now return 10 release nodes per query.

[lucasmdrs]

Looks good

It's a bit hard to be sure since the behavior was not documented before, but from the examples I agree with your interpretation of the param amount.