ITEP-87923: Validate user password and username API fields

[daddo-intel]

📝 Description

Small change to serializer.py to validate password and username API fields for user

✨ Type of Change

Select the type of change your PR introduces:

• 🐞 Bug fix – Non-breaking change which fixes an issue
• 🚀 New feature – Non-breaking change which adds functionality
• 🔨 Refactor – Non-breaking change which refactors the code base
• 💥 Breaking change – Changes that break existing functionality
• 📚 Documentation update
• 🔒 Security update
• 🧪 Tests
• 🚂 CI

🧪 Testing Scenarios

Describe how the changes were tested and how reviewers can test them too:

• ✅ Tested manually
• 🤖 Ran automated end-to-end tests

✅ Checklist

Before submitting the PR, ensure the following:

• 🔍 PR title is clear and descriptive
• 📝 For internal contributors: If applicable, include the JIRA ticket number (e.g., ITEP-123456) in the PR title. Do not include full URLs
• 💬 I have commented my code, especially in hard-to-understand areas
• 📄 I have made corresponding changes to the documentation
• ✅ I have added tests that prove my fix is effective or my feature works

[sbelhaik]

@daddo-intel The user can be created with invalid scene uid

[daddo-intel]

@daddo-intel The user can be created with invalid scene uid

Not sure I understand this comment

[sbelhaik]

@daddo-intel The user can be created with invalid scene uid

Not sure I understand this comment

The user definition in spec includes scene property, however, when creating a user with username, password and scene, it ignores scene field and creates user without validating whether the provided scene is valid.

[Copilot]

Pull request overview

Adds object-level validation to the Manager service’s UserSerializer to enforce username/password presence on user creation and prevent blank values when those fields are updated.

Changes:

• Add UserSerializer.validate() to require username and password on create.
• Add update-time checks to reject blank username / password when those keys are provided in the request.

[daddo-intel]

@daddo-intel The user can be created with invalid scene uid

Not sure I understand this comment

The user definition in spec includes scene property, however, when creating a user with username, password and scene, it ignores scene field and creates user without validating whether the provided scene is valid.

The scene field is not needed when creating a user. Will update the spec