fix: background mview without backfilling should not tracked in barrier runtime info

[yezizp2012]

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

What's changed and what's your intention?

Fixed a bug found in https://buildkite.com/risingwavelabs/main-cron/builds/3843#01931e2c-869a-4314-aa99-849e4747f72c, will open another PR to fix release-2.0.

As title, we need to complete the background materialized view without backfilling during recovery; otherwise, it will be logged in the barrier runtime information and remain unfinished because of the absence of progress reports from actors. Similar logic in normal creation:

risingwave/src/meta/src/barrier/progress.rs

Lines 511 to 516 in 3c2e81b

	if actors.is_empty() {
	// The command can be finished immediately.
	return Some(TrackingJob::New(TrackingCommand {
	info: info.clone(),
	replace_table_info: replace_table.cloned(),
	}));

Furthermore, it should be noted that Value cannot be recovered and is not permitted in background mode.

risingwave/src/frontend/src/optimizer/plan_node/utils.rs

Lines 394 to 398 in 58ecec2

	/// Check that all leaf nodes must be stream table scan,
	/// since that plan node maps to `backfill` executor, which supports recovery.
	/// Some other leaf nodes like `StreamValues` do not support recovery, and they
	/// cannot use background ddl.
	pub(crate) fn plan_can_use_background_ddl(plan: &PlanRef) -> bool {

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.

[wenym1]

LGTM

[kwannoel]

LGTM thanks