ftl-project.toml loaded even if a different project file is specified

[wesbillman]

If we have 2 ftl-project.toml files (notice op:// used in first file). And we specify with ftl dev ... that we want to use ftl-project-inline.toml it seems like the code is still loading the base ftl-project.toml file even though we didn't specify it. This leads to issues where 1Password needs to be configured even though we're online using inline secrets.

ftl dev examples/go --recreate --config=ftl-project.toml,ftl-project-inline.toml

info: Starting FTL with 1 controller(s)
info:controller0: Web console available at: http://localhost:8892
info: ftl-project-inline.toml startup command ⚡️
info:time: Building module
info:echo: Building module
info:time: Deploying module
info:echo: Deploying module
error:echo: main: error: could not get config: internal: could not marshal module context: failed to get config map: no provider for scheme "op"
warn:echo: Plugin failed to start, terminating pid 69894

# ftl-project.toml
module-dirs = ["examples/go"]
external-dirs = []

[global]

[modules]
[modules.echo]
[modules.echo.configuration]
default = "op://ImFub255bW91cyI"

[commands]
startup = ["echo 'ftl-project.toml startup command ⚡️'"]

# ftl-project-inline.toml
module-dirs = ["examples/go"]
external-dirs = []

[global]

[modules]
[modules.echo]
[modules.echo.configuration]
default = "inline://ImFub255bW91cyI"

[commands]
startup = ["echo 'ftl-project-inline.toml startup command ⚡️'"]