Increase timeout on fuzzing deployment pipeline

[MihaZupan]

This issue unfortunately still exists:

runtime/eng/pipelines/libraries/fuzzing/deploy-to-onefuzz.yml

Lines 57 to 66 in 265727c

	# OneFuzz can't currently handle a single deployment where multiple jobs share similar assemblies/pdbs.
	# As a workaround, we emit a task for every fuzzing target individually.
	# https://fuzzfest.visualstudio.com/Onefuzz/_workitems/edit/191504/ is tracking this issue.
	# - task: onefuzz-task@0
	# inputs:
	# onefuzzOSes: 'Windows'
	# env:
	# onefuzzDropDirectory: $(fuzzerProject)/deployment
	# SYSTEM_ACCESSTOKEN: $(System.AccessToken)
	# displayName: Send to OneFuzz

Forcing us to send fuzzers over one by one. Now that we've added more fuzzers, we're occasionaly hitting the 120 minute timeout.
https://dev.azure.com/dnceng/internal/_build?definitionId=1381&_a=summary

(this pipeline runs once a day to update the build of runtime used by OneFuzz infra)

[Copilot]

Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.

[dotnet-policy-service]

Tagging subscribers to this area: @dotnet/area-infrastructure-libraries
See info in area-owners.md if you want to be subscribed.