Extend to 3 hours

[sima-zhu]

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.
Java docindex validate and update package info once the version changes. We usually ran into traffic peak during the monthly release. Extend the pipeline to 3 hours to take care of the timeout.
https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1958961&view=results
If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[weshaggard]

I'm ok increasing the timeout as long as feel like there isn't any work we can cut out.

[sima-zhu]

I'm ok increasing the timeout as long as feel like there isn't any work we can cut out.

The validation step takes time but lucky this only happens every month.