Increased timeout value for delete history event task

[timl3136]

What changed?
We increased the timeout value for delete history event task to dynamic config with default at 30s.

Why?
The timeout value for delete history event is too low causing large history deletion to constantly timeout

How did you test it?

Potential risks

Release notes

Documentation Changes

[codecov]

Codecov Report

Merging #5888 (c90219f) into master (65c4017) will decrease coverage by 0.08%.
The diff coverage is 100.00%.

❗ Current head c90219f differs from pull request most recent head 24b8346. Consider uploading reports for the commit 24b8346 to get more accurate results

Additional details and impacted files

Files	Coverage Δ
service/history/task/timer_active_task_executor.go	72.00% <100.00%> (+0.49%)	⬆️
...ervice/history/task/timer_standby_task_executor.go	78.94% <100.00%> (+0.98%)	⬆️
...ervice/history/task/transfer_task_executor_base.go	81.73% <ø> (ø)

... and 10 files with indirect coverage changes

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 65c4017...24b8346. Read the comment docs.

[coveralls]

Pull Request Test Coverage Report for Build 018ec3d7-42d3-4387-8cf7-9808097685ae

Details

• 9 of 9 (100.0%) changed or added relevant lines in 3 files are covered.
• 37 unchanged lines in 11 files lost coverage.
• Overall coverage increased (+0.02%) to 67.363%

---

Files with Coverage Reduction	New Missed Lines	%
service/matching/taskReader.go	2	84.88%
common/persistence/sql/sqlplugin/postgres/task.go	2	73.4%
service/history/shard/context.go	2	66.7%
common/persistence/sql/sqlplugin/postgres/db.go	2	80.0%
service/history/task/transfer_active_task_executor.go	2	72.7%
common/membership/hashring.go	2	84.69%
service/matching/taskListManager.go	3	79.7%
service/history/task/transfer_standby_task_executor.go	4	86.6%
service/history/task/task_util.go	4	75.14%
common/task/fifo_task_scheduler.go	7	82.47%

Totals
Change from base Build 018ec2d0-2d55-4385-9005-feae08321986:	0.02%
Covered Lines:	98199
Relevant Lines:	145776

---

💛 - Coveralls

[taylanisikdemir]

I know the existing ctx has 3 sec timeout and doesn't listen for queue shut down signals.
With the new 60s timeout for history deletions it is going to be more likely to end up hanging a shutdown. We should consider making these operations responsive to shut down signals.
@Shaddoll what do you think?

[taylanisikdemir]

Discussed offline. We will hook up Stop signals to task executor in a follow up PR.
In this PR, let's make this 60s dynamically configurable