passing extra compilation flags with coffee

I think that we need a way to pass some custom parameters down the road to give some templating to pass down some env information

```
➜ ~ coffee install summars -v
Compiling icu_datetime_data v1.4.0
Compiling cln-rpc v0.1.8
Compiling struct-field-names-as-array v0.3.0
Compiling cln-plugin v0.1.8
error: could not compile `icu_datetime_data` (lib)

Caused by:
process didn't exit successfully: `/home/vincent/.rustup/toolchains/stable-x86_64-unknown-linux-gnu/bin/rustc --crate-name icu_datetime_data --edition=2021 /home/vincent/.cargo/registry/src/index.crates.io-6f17d22bba15001f/icu_datetime_data-1.4.0/src/lib.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=104 --crate-type lib --emit=dep-info,metadata,link -C opt-level=3 -C embed-bitcode=no -C metadata=69d1c3cbabc16994 -C extra-filename=-69d1c3cbabc16994 --out-dir /home/vincent/.coffee/bitcoin/plugins/summars/target/release/deps -L dependency=/home/vincent/.coffee/bitcoin/plugins/summars/target/release/deps --cap-lints allow` (signal: 9, SIGKILL: kill)
warning: build failed, waiting for other jobs to finish...
Building [=======================> ] 147/153: cln-rpc
```

The plugin info are there

```
➜ ~ coffee remote list
● List of repositories
╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ ● Repository Alias URL N. Plugins Git HEAD Last Update │
├──────────────────────────────────────────────────────────────────────────────────────────────────────┤
│ ● folgore-git https://github.com/coffee-tools/folgore 1 aedd703 12/03/2024 │
│ ● summars https://github.com/daywalker90/summars 1 c73633a 18/03/2024 │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────╯
```

Start by tracing the `coffee install summars -v` command and the Rust compilation invocation shown in the report; the repository and plugin information from `coffee remote list` provides the example case. Define how custom compilation parameters should be supplied and verify that they reach the plugin build while preserving the existing install flow.

Written by the indexing model from the issue text.