docs: update swagger path

A recent commit b6f4636 relocated swagger definition file, but missed
updating links to it in documentations.

Fixed it by search and replace:
  git grep -l -e api_server/swagger --and --not -e src/api_server/swagger \
    | xargs sed -i 's:api_server/swagger:src/api_server/swagger:'

Fixes: b6f4636 ("build: workspace cleanup")
Signed-off-by: Zi Shen Lim <[email protected]>

Author: zlim

README.md

@@ -85,7 +85,7 @@ Firecracker's overall architecture is described in
 
 Firecracker consists of a single micro Virtual Machine Manager process that
 exposes an API endpoint to the host once started. The API is
-[specified in OpenAPI format](api_server/swagger/firecracker.yaml). Read more
+[specified in OpenAPI format](src/api_server/swagger/firecracker.yaml). Read more
 about it in the [API docs](docs/api_requests).
 
 The **API endpoint** can be used to:

SPECIFICATION.md

@@ -18,7 +18,7 @@ enough RAM, etc.), customers can rely on the following:
    they are logged³ by the Firecracker process.
 1. **API Stability:** The API socket is always available and the API conforms
    to the in-tree
-   [Open API specification](api_server/swagger/firecracker.yaml). API failures
+   [Open API specification](src/api_server/swagger/firecracker.yaml). API failures
    are logged in the Firecracker log.
 1. **Overhead:** For a Firecracker virtual machine manager running a microVM
    with `1 CPUs and 128 MiB of RAM`, and a guest OS with the Firecracker-tuned

docs/api_requests/actions.md

@@ -4,7 +4,7 @@ Firecracker microVMs can execute actions that can be triggered via `PUT`
 requests on the `/actions` resource.
 
 Details about the required fields can be found in the
-[swagger definition](../../api_server/swagger/firecracker.yaml).
+[swagger definition](../../src/api_server/swagger/firecracker.yaml).
 
 ## BlockDeviceRescan
 

docs/api_requests/logger.md

@@ -21,7 +21,7 @@ curl --unix-socket /tmp/firecracker.socket -i \
 ```
 
 Details about the required and optional fields can be found in the
-[swagger definition](../../api_server/swagger/firecracker.yaml).
+[swagger definition](../../src/api_server/swagger/firecracker.yaml).
 
 The `logs.fifo` file stores the human readable logs (i.e errors,
 warnings etc) while the `metrics.fifo` file stores the metrics

docs/api_requests/patch-network-interface.md

@@ -58,7 +58,7 @@ Accept: application/json
 ```
 
 The full specification of the data structures available for this call can be
-found in our [OpenAPI spec](../../api_server/swagger/firecracker.yaml).
+found in our [OpenAPI spec](../../src/api_server/swagger/firecracker.yaml).
 
 **Note**: The data provided for the update is merged with the existing data.
 In the above example, the RX rate limit is updated, but the TX rate limit