[Improvement-18403][API&Security] Avoid raw password exposure in user parameter validation errors

[njnu-seafish]

Was this PR generated or assisted by AI?

NO

Purpose of the pull request

close #18403

Brief change log

Avoid raw password exposure in user parameter validation errors

Verify this pull request

This pull request is code cleanup without any test coverage.

(or)

This pull request is already covered by existing tests, such as (please describe tests).

(or)

This change added tests and can be verified as follows:

(or)

Pull Request Notice

Pull Request Notice

If your pull request contains incompatible change, you should also add it to docs/docs/en/guide/upgrade/incompatible.md

[njnu-seafish]

@SbloodyS I noticed some inconsistencies in the naming and placement of the test classes while looking through the code.

The service tests in the dolphinscheduler-api module currently have inconsistent naming and package placement. Most tests are placed under org.apache.dolphinscheduler.api.service, but they directly test implementation classes such as UsersServiceImpl, ProjectServiceImpl, and QueueServiceImpl. Meanwhile, a few similar tests are placed under org.apache.dolphinscheduler.api.service.impl. The class names are also inconsistent: some use the XxxServiceImplTest pattern, while most use XxxServiceTest even though they test XxxServiceImpl directly. This makes the test structure harder to navigate and maintain.

Would it be worth standardizing these tests by moving service implementation tests under api.service.impl and renaming them to XxxServiceImplTest?

[SbloodyS]

These don't need to be modified for the time being. @njnu-seafish

[SbloodyS]

LGTM

[njnu-seafish]

These don't need to be modified for the time being

ok