Do not use multicall for individual Beacon updates

[bbenligiray]

This adds an unnecessary gas cost overhead for individual Beacon updates, which is quite important for self-funded feeds

[bbenligiray]

@metobom same with api3dao/airseeker#448 (comment)

[acenolaza]

@bbenligiray at first I understood that we should not use tryMulticall on updateBeacons() when the count of update calldatas is equal to 1 but after re-reading the title and description on the issue I'm now thinking that the expected change is to just remove the tryMulticall altogether from updateBeacons(). Is this right?

[bbenligiray]

at first I understood that we should not use tryMulticall on updateBeacons() when the count of update calldatas is equal to 1

This is right

If there are 11 Beacons to be updated and we're updating them in batches of 10, we can also omit the tryMulticall() of the second batch with a single Becaon update. It feels like this would also reduce code duplication in your implementation.