watcher: Enable skipped tests

The PR #88 enables watcher, although some tests are skipped. They need to be analyzed and check if they can be enabled.

```
{2} setUpClass (watcher_tempest_plugin.tests.api.admin.test_action.TestPatchAction) ... SKIPPED: The microversion range[1.5 - latest] of this test is out of the configuration range[None - None].
{2} setUpClass (watcher_tempest_plugin.tests.api.admin.test_audit.TestCreateUpdateDeleteAuditV11) ... SKIPPED: The microversion range[1.1 - latest] of this test is out of the configuration range[None - None].
{0} setUpClass (watcher_tempest_plugin.tests.api.admin.test_data_model.TestListDataModel) ... SKIPPED: The microversion range[1.3 - latest] of this test is out of the configuration range[None - None].
{3} setUpClass (watcher_tempest_plugin.tests.api.admin.test_audit.TestCreateUpdateDeleteAuditV14) ... SKIPPED: The microversion range[1.4 - latest] of this test is out of the configuration range[None - None].
{4} setUpClass (watcher_tempest_plugin.tests.api.admin.test_data_model.TestNegativeListDataModel) ... SKIPPED: The microversion range[1.3 - latest] of this test is out of the configuration range[None - None].
```

Start by running the five skipped test classes listed in the issue under watcher_tempest_plugin.tests.api.admin and inspect their microversion configuration and skip conditions. Determine why each configured range is None - None; done means the tests that are compatible with the environment are enabled and pass, while incompatible cases have a documented reason to remain skipped.

Written by the indexing model from the issue text.