nim-waku external files and resources

[jm-clius]

Problem

In some places nim-waku code references versioned controlled files/resources in an ad-hoc manner. For example, migration loads migrations scripts from the source code directory, while RLN references a file in the /vendor/ subdirectory. These are sometimes added, sometimes not, to the docker image, leading to bugs and inconsistencies.

Solution

Proper resources management, with all resources being made available in a resources/ subdirectory that is always included in the docker image and PATH.

Acceptance criteria

• External resources for wakunode2 (including for RLN) all reside in a single place.
• Docker image updated to reference this path

[jm-clius]

Closing. RLN can now be statically compiled. Migration scripts are being moved to external process by DB operator. Similar issue with postgresql dependency being addressed here: #1839