VS Code Testing Config (#38)

<!-- markdownlint-disable-next-line first-line-heading -->
## Description

<!-- Describe your changes in detail. -->
This defaults the testing configuration within VS Code, so that tests
are automatically discovered via the Testing tab.

## Context

<!-- Why is this change required? What problem does it solve? -->
It allows for easier execution of the tests if potential users don't
want to use the command line all the time.

## Type of changes

<!-- What types of changes does your code introduce? Put an `x` in all
the boxes that apply. -->

- [ ] Refactoring (non-breaking change)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would change existing
functionality)
- [ ] Bug fix (non-breaking change which fixes an issue)

## Checklist

<!-- Go over all the following points, and put an `x` in all the boxes
that apply. -->

- [x] I am familiar with the [contributing
guidelines](https://github.com/nhs-england-tools/playwright-python-blueprint/blob/main/CONTRIBUTING.md)
- [x] I have followed the code style of the project
- [ ] I have added tests to cover my changes (where appropriate)
- [x] I have updated the documentation accordingly
- [ ] This PR is a result of pair or mob programming

---

## Sensitive Information Declaration

To ensure the utmost confidentiality and protect your and others
privacy, we kindly ask you to NOT including [PII (Personal Identifiable
Information) / PID (Personal Identifiable
Data)](https://digital.nhs.uk/data-and-information/keeping-data-safe-and-benefitting-the-public)
or any other sensitive data in this PR (Pull Request) and the codebase
changes. We will remove any PR that do contain any sensitive
information. We really appreciate your cooperation in this matter.

- [x] I confirm that neither PII/PID nor sensitive data are included in
this PR and the codebase changes.

Author: davethepunkyone

.vscode/settings.json

@@ -21,5 +21,10 @@
     "utilise",
     "utilised",
     "Utilising"
-  ]
+  ],
+  "python.testing.pytestArgs": [
+    "."
+  ],
+  "python.testing.unittestEnabled": false,
+  "python.testing.pytestEnabled": true
 }

README.md

@@ -57,6 +57,9 @@ so you can see the browser execution):
 pytest --tracing on --headed
 ```
 
+Alternatively if you are using Visual Studio Code as your IDE, we have pre-configured this project to work with the
+[Testing functionality](https://code.visualstudio.com/docs/editor/testing) so the example tests should be discovered automatically.
+
 ## Getting Started
 
 > NOTE: This section is currently under development and requires further work, so links to pages within this repository may not be very useful at this stage.