RHCLOUD-37616 - Added ability to filter service accounts by na…

[EvanCasey13]

…me, owner or description. Added tests cases for service account filtering

Link(s) to Jira

https://issues.redhat.com/browse/RHCLOUD-29904

Description of Intent of Change(s)

Implemented filtering for service accounts on name, owner and description with test cases for filtering. Implemented sorting of service accounts by Service Account Name, Description, Client ID, Owner & Time created both ascending and descending.

Local Testing

How can the feature be exercised?
Running this curl commands replacing the filtering parameter with the valid fields of name, owner or description.

curl -v "http://localhost:8000/api/rbac/v1/principals/?type=service-account&name=e6921ca0-9cd3-013c-1dc6-6aa2427b506a-name" -H "accept: application/json" | json_pp

How can the bug be exploited and fix confirmed?
Is any special local setup required?

Checklist

• if API spec changes are required, is the spec updated?
• are there any pre/post merge actions required? if so, document here.
• are theses changes covered by unit tests?
• if warranted, are documentation changes accounted for?
• does this require migration changes?
  • if yes, are they backwards compatible?
• is there known, direct impact to dependent teams/components?
  • if yes, how will this be handled?

Secure Coding Practices Checklist Link

• https://github.com/RedHatInsights/secure-coding-checklist

Secure Coding Practices Checklist

• Input Validation
• Output Encoding
• Authentication and Password Management
• Session Management
• Access Control
• Cryptographic Practices
• Error Handling and Logging
• Data Protection
• Communication Security
• System Configuration
• Database Security
• File Management
• Memory Management
• General Coding Practices

[vbelchio]

@EvanCasey13 Probably do we need to update the OpenAPI specs to add the options, don't we?