TestSystemThrottler test flake

[StephenButtolph]

Describe the bug

Seems like there is a flaky test:

--- FAIL: TestSystemThrottler (0.82s)
    inbound_resource_throttler_test.go:130: 
        	Error Trace:	/Users/runner/work/avalanchego/avalanchego/network/throttling/inbound_resource_throttler_test.go:130
        	Error:      	should have returned after about [maxRecheckDelay]
        	Test:       	TestSystemThrottler
    controller.go:269: missing call(s) to *tracker.MockTargeter.TargetUsage(is equal to NodeID-3EByCvwM8xayYrNJpzqkKtUdnEszJDbEq (ids.NodeID)) /Users/runner/work/avalanchego/avalanchego/network/throttling/inbound_resource_throttler_test.go:116
    controller.go:269: missing call(s) to *tracker.MockTracker.Usage(is equal to NodeID-3EByCvwM8xayYrNJpzqkKtUdnEszJDbEq (ids.NodeID), is anything) /Users/runner/work/avalanchego/avalanchego/network/throttling/inbound_resource_throttler_test.go:117
    controller.go:269: aborting test due to missing call(s)
FAIL
coverage: 82.3% of statements
FAIL	github.com/ava-labs/avalanchego/network/throttling	3.635s

[github-actions]

This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

[joshua-kim]

I don't think our CI has been flaking due to this anymore, closing this issue.