Go builds are queing up rather than building once

[matt2e]

Steps to repro:

• ftl dev
• Modify a file in a go module once per second for a while
• Look at what FTL is doing

Expected result:

• FTL will notice all the file changes and then attempt a build as long as there have been updates since the last build

Actual Result:

• Each saved change schedules another build

[matt2e]

Not sure how to repro.
I wonder if there are multiple build calls happening at once? That'd explain why each one has an increasing duration as it waits for a flock on the module...