Prepare plugin for v4 API

[aKlimau]

Update viewsets to accept **kwargs, fix hardcoded v3 urls.
https://redhat.atlassian.net/browse/PULP-2189

📜 Checklist

• Commits are cleanly separated with meaningful messages (simple features and bug fixes should be squashed to one commit)
• A changelog entry or entries has been added for any significant changes
• Follows the Pulp policy on AI Usage
• (For new features) - User documentation and test coverage has been added

See: Pull Request Walkthrough

[ggainey]

👍

[ggainey]

Change looks good - approved

[jobselko]

test_domain_object_creation in test_domains.py hardcodes v3 in an assertion

[ggainey]

test_domain_object_creation in test_domains.py hardcodes v3 in an assertion

Yes - but that's a global issue. See https://redhat.atlassian.net/browse/PULP-2220 - I want us to have a way for the tests to know what version of the API they are running against, so we can replace assertions with '/v3/' in them with something like '/VERSION/' and have everything Just Work.

Asserting on strings that don't require the version-part, or substituting /v\d+/, is fine as well - but def want 2220 in next sprint, so we can have more-version-aware testing :)

[jobselko]

@ggainey Thanks for the clarification! So are you ok with fixing the test now? Or should we revert the change?

[ggainey]

@ggainey Thanks for the clarification! So are you ok with fixing the test now? Or should we revert the change?

Current state is fine. Since the test is really "does the domain-name show up in the HREF", and doesn't actually care about the version, this is better at defining what we're actually testing for. So we're good :)