[BugFix] fix ingestion hang because of alter job timeout

[luohaha]

Why I'm doing:

In shared-data cluster, alter job will increase partition's next version and then change state to FINISHED_REWRITING. But if this alter job is timeout, it won't be executed and can't finish, it will lead to version gap and cause issue like:

2025-01-13 05:13:26.728Z ERROR (lake-publish-task-160840|200302) [PublishVersionDaemon.publishPartitionBatch():488] publish partition batch partition.getVisibleVersion() + 1 != version.get(0) 4473684 37071 37073

What I'm doing:

Two changes in my PR:

1. Only skip the alter job which can be cancelled.
2. Fix timeout setting when create LakeTableAlterMetaJob.

This pull request includes changes to improve the handling of job cancellation and timeouts in the AlterJobV2 class, as well as a minor adjustment to the timeout parameter in the SchemaChangeHandler class. The most important changes are summarized below:

Improvements to job cancellation handling:

• fe/fe-core/src/main/java/com/starrocks/alter/AlterJobV2.java: Modified the run method to handle job cancellation more effectively by checking if the job can be cancelled and executing it if not.

Adjustments to timeout parameter:

• fe/fe-core/src/main/java/com/starrocks/alter/SchemaChangeHandler.java: Changed the timeout parameter for LakeTableAlterMetaJob from seconds to milliseconds to ensure accurate timeout handling.

What type of PR is this:

• BugFix
• Feature
• Enhancement
• Refactor
• UT
• Doc
• Tool

Does this PR entail a change in behavior?

• Yes, this PR will result in a change in behavior.
• No, this PR will not result in a change in behavior.

If yes, please specify the type of change:

• Interface/UI changes: syntax, type conversion, expression evaluation, display information
• Parameter changes: default values, similar parameters but with different default values
• Policy changes: use new policy to replace old one, functionality automatically enabled
• Feature removed
• Miscellaneous: upgrade & downgrade compatibility, etc.

Checklist:

• I have added test cases for my bug fix or my new feature
• This pr needs user documentation (for new or modified features or behaviors)
  • I have added documentation for my new feature or new function
• This is a backport pr

Bugfix cherry-pick branch check:

• I have checked the version labels which the pr will be auto-backported to the target branch
  • 3.4
  • 3.3
  • 3.2
  • 3.1
  • 3.0

[github-actions]

[FE Incremental Coverage Report]

❌ fail : 4 / 6 (66.67%)

file detail

	path	covered_line	new_line	coverage	not_covered_line_detail
🔵	com/starrocks/alter/RollupJobV2.java	0	1	00.00%	[773]
🔵	com/starrocks/alter/AlterJobV2.java	4	5	80.00%	[272]

[sonarqubecloud]

Quality Gate passed

Issues
6 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
20.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

[Java-Extensions Incremental Coverage Report]

✅ pass : 0 / 0 (0%)

[github-actions]

[BE Incremental Coverage Report]

✅ pass : 0 / 0 (0%)