refine: erase unneed audio operation & fix potential bug

[bofeng-song]

Re: # https://github.com/cocos/3d-tasks/issues/7318

Changelog

---

Continuous Integration

This pull request:

• needs automatic test cases check.

  Manual trigger with @cocos-robot run test cases afterward.

• does not change any runtime related code or build configuration

  If any reviewer thinks the CI checks are needed, please uncheck this option, then close and reopen the issue.

---

Compatibility Check

This pull request:

• changes public API, and have ensured backward compatibility with deprecated features.
• affects platform compatibility, e.g. system version, browser version, platform sdk version, platform toolchain, language version, hardware compatibility etc.
• affects file structure of the build package or build configuration which requires user project upgrade.
• introduces breaking changes, please list all changes, affected features and the scope of violation.

[PPpro]

where we used this class, can we use the OperationInfo exported from operation-queue.ts ? or should it be an interface ?

[bofeng-song]

Used by _operationsBeforeLoading

[bofeng-song]

AudioSource only needs two variables, a function name and a parameter; it does not require as many parameter requirements as operation-queue.

[PPpro]

could it be an interface instead of a class， I see you only use it as an interface, which is only a type
but class will exist in runtime

[PPpro]

this emit message means the operation is finished, are you sure ?

[bofeng-song]

I known, what potential problems will it cause?

[bofeng-song]

Currently, only the play interface has a then processing.
this.node?.emit(AudioSourceEventType.STARTED, this);

[PPpro]

we only emit the finished message when the operation is finished, see the line no 49

cocos-engine/pal/audio/operation-queue.ts

Lines 46 to 52 in f024d3f

	opInfo.func.call(target, ...opInfo.args).then(() => {
	opInfo.invoking = false;
	target._operationQueue.shift();
	target._eventTarget.emit(opInfo.id.toString());
	const nextOpInfo: OperationInfo = target._operationQueue[0];
	nextOpInfo && _tryCallingRecursively(target, nextOpInfo);
	}).catch((e) => {});

Otherwise, the call order of the queue will be messed up.

[minggo]

_player? -> _player as it is checked in if condition.

[minggo]

And please fix the ESLint error.

[minggo]

It is better to use state machine for these operations in future.