Incorrectly fetches versions when initial_build_id is lower than earliest build

[jchesterpivotal]

Problem

If I set initial_build_id to 100, but the earliest global build number visible for a team/pipeline/job combination is 101, the resource will "hang" after fetching version 100. This is because I use since as my search parameter, which returns an empty array for build IDs that are below its range.

Solution

Use limit=1 and until=1 to find the earliest version visible for a given team/pipeline/job. If it is above initial_build_id, use that number instead.