feat(compaction): introduce new task status for serverless compaction

[Li0k]

I hereby agree to the terms of the RisingWave Labs, Inc. Contributor License Agreement.

What's changed and what's your intention?

related to https://github.com/risingwavelabs/risingwave-extensions/blob/main/pkg/compaction/drive/driver.go

The driver changes the task status in two ways

1. Send faill https://github.com/risingwavelabs/risingwave-extensions/blob/123845fc61d9815216e6647173e2af2c6e4c94cd/pkg/compaction/drive/driver.go#L312
2. Unable to fetch the table catalogs for the task https://github.com/risingwavelabs/risingwave-extensions/blob/123845fc61d9815216e6647173e2af2c6e4c94cd/pkg/compaction/drive/driver.go#L403

This PR introduces a separate task status type to serve the serverless compaction module, to make it easier to distinguish the source of the error.

cloud side: https://github.com/risingwavelabs/risingwave-extensions/issues/66

Checklist

• I have written necessary rustdoc comments
• I have added necessary unit tests and integration tests
• I have added test labels as necessary. See details.
• I have added fuzzing tests or opened an issue to track them. (Optional, recommended for new SQL features Sqlsmith: Sql feature generation #7934).
• My PR contains breaking changes. (If it deprecates some features, please create a tracking issue to remove them in the future).
• All checks passed in ./risedev check (or alias, ./risedev c)
• My PR changes performance-critical code. (Please run macro/micro-benchmarks and show the results.)

• My PR contains critical fixes that are necessary to be merged into the latest release. (Please check out the details)

Documentation

• My PR needs documentation updates. (Please use the Release note section below to summarize the impact on users)

Release note

If this PR includes changes that directly affect users or other significant modifications relevant to the community, kindly draft a release note to provide a concise summary of these changes. Please prioritize highlighting the impact these changes will have on users.

[hzxa21]

Will serverless compaction controller add more error codes in the future? I am thinking whether we should have one error code only for all serverless compaction controller error.

[arkbriar]

Will serverless compaction controller add more error codes in the future?

I think it's possible, but not in a near future since the serverless protocol won't change frequently.

I am thinking whether we should have one error code only for all serverless compaction controller error.

I'm fine if the error message isn't lost. But seems we rely on the error code to tell the error kind, I think we'd better add more when necessary.

[Li0k]

I think it depends on whether we introduce more state to the compact task, e.g. table_catalog. As we iterate through the logic of the compact task, we may introduce more corresponding error

[hzxa21]

LGTM