### Summary
In some cases, the query parameters for a MongoDB aggregation pipeline were not being initialized.
This led to errors in `GET /api/v1/vaas/{chain}/{emitter}/{seq}`.
Other endpoints could also have been affected.
Previously, when calling `GET /api/v1/governor/enqueued_vaas`, it returned a status code of 404 when there were no enqueued VAAs.
Now, the endpoint returns a status code of 200, and the response body contains an empty array.
### Summary
* On all endpoints, fix the behavior of the `page` parameter (which was previously being ignored).
* On `GET /api/v1/vaas`, fix the behavior of the `sortBy` parameter (which wasn't working when `parsedPayload=true`).
* For all endpoints, validate the query parameters `page`, `pageNumber` and `sortOrder`.
* Return descriptive errors when pagination-related parameters happen to be invalid (`page`, `pageSize`, `sortOrder`).
* Validate guardian addresses in query params.
### Testing plan
All parameters involved were manually tested.
### Summary
Before this PR, when validating a VAA, we were always using the latest guardian set index to verify the signatures.
With this PR, we're making the signature verification against `vaa.guardianSetIndex` instead.
Context: https://github.com/wormhole-foundation/wormhole-explorer/issues/104
### Testing plan
* Added unit test cases
* Also tested manually
### Summary
Split `/v1` and `/api/v1` controllers into different packages (respectively `api/routes/guardian` and `api/routes/wormscan`).
Still need to move services/repositories/models according to the new package layout.
### Summary
Updating from swaggo v1.8.9 to v1.8.10 caused issues with the generated swagger file.
The issue was solved by moving the handler for `GET /swagger.json` outside the `/doc` directory.
* add vaaId and txHash relation in vaaIdTxHash collection
* add txHash in vaas collection
* add txHash in response vaa and as filter in find vaas endpoints
* Add pipeline to parse vaa
* Add parser repository and start building pipeline publisher
* Add queue sqs and in-memory to pipeline
* Add ses publisher and queue sqs/memory
* Fix watcher query
* Fix type to marshall/unsmarshall chainID and emitterAddress
* Fix js execution is run many times
* Add comments
* Add comments and improvements
* Change VAA Parser implementation
* Fix and change integration-test vaa-payload-parser
* fix appID mongo field name
* Fix guardianSet version 3, add xlabs to position 8
Co-authored-by: Agustin Pazos <agpazos85@gmail.com>