Parse tome paramdefs on startup

[hulto]

What type of PR is this?:

/kind bug

What this PR does / why we need it:

• Switches the tome name to use the metadata file instead of file name.
• Calls SetParamDefs during tome parsing
• Updated the example metadata.yml file with example paramdefs.
• Increases the max length of the param defs field form 256 bytes to 4GB

Which issue(s) this PR fixes:

Fixes #295

[alexcote1]

Looks good, glad that static hello world is no longer there

[Jorgey7]

What did meowware ever do to you smh

[hulto]

Broke my heart 💔

[KCarretto]

We can make the paramdefs be more readable in the yaml, e.g.

'''
paramdefs:

• name: msg
  label: Message
  '''

[hulto]

We can make the paramdefs be more readable in the yaml, e.g.

'''
paramdefs:

• name: msg
  label: Message
  '''

I can play with it more but when I tried that ^ it doesn't parse right since I think everything is expecting a JSON string.
We could do some gross reparsing to turn the yaml into a JSON string.

[codecov]

Codecov Report

Merging #298 (d302962) into main (7ffe6ba) will decrease coverage by 0.05%.
The diff coverage is 64.00%.

@@            Coverage Diff             @@
##             main     #298      +/-   ##
==========================================
- Coverage   74.84%   74.80%   -0.05%     
==========================================
  Files          94       94              
  Lines        6106     6131      +25     
==========================================
+ Hits         4570     4586      +16     
- Misses       1450     1458       +8     
- Partials       86       87       +1     

Files	Coverage Δ
implants/imix/src/main.rs	77.81% <100.00%> (+0.04%)	⬆️
implants/lib/eldritch/src/lib.rs	92.75% <ø> (ø)
tavern/internal/ent/schema/quest.go	38.77% <100.00%> (+3.99%)	⬆️
tavern/internal/ent/schema/tome.go	67.16% <100.00%> (+1.53%)	⬆️
tavern/tomes/parse.go	51.68% <50.00%> (-0.43%)	⬇️

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[hulto]

Actually I think we should prioritize consistency between the standard tomes and uploaded tomes.
Since uploaded tomes require paramDefs be a JSON string we should keep the standard ones with the JSON string.

If we want to re-do paramDefs to not be a JSON string we can do that later but for now I think we should stick with the agreed on paramDefs format.

[hulto]

Gonna pass to @cmp5987
Looks like the front end isn't passing paramdefs rn.

parameters: Some(r#"{"cmd":"echo main_loop_test_success"}"#.to_string())

We need to add the "parameters" field to the formatVariables in the createQuestMutation
The parameters value should be a JSON string following the format {"key_name":"key_value"}

@cmp5987 pointed out this is confusing especially since the defs follow the pattern: {"name":"key_name","type":"type_value_type"} which is a more standard way to use objects.

The params, and paramdefs work flow should probably be re-worked at a later date so we're not using JSON strings at all.

[hulto]

Working now had to pass the params the right way.

[hulto]

Issue with golang.

$ cat /tmp/port_scan/metadata.yml 
name: Port scan
description: Scan a list of ports in a list of CIDRs.
paramdefs: "[{\"name\":\"cidrs\",\"label\":\"CIDRs\",\"type\":\"string\",\"placeholder\":\"['192.168.0.0./24','10.102.9.11/32']\"},{\"name\":\"ports\",\"label\":\"Ports\",\"type\":\"list\",\"placeholder\":\"[22,80,443]\"},{\"name\":\"protocol\",\"label\":\"Protocol\",\"type\":\"string\",\"placeholder\":\"tcp\"},{\"name\":\"timeout\",\"label\":\"Timeout\",\"type\":\"int\",\"placeholder\":\"2\"]"%                                                                                                                                                    ```

[hulto]

• add a test to parse go that validates passing no "paramdefs" is valid.