fix!: remove broken configPath option

[FabianLars]

This may seem extreme at first but let's be honest, this option never did what you expect and removing it will move it closer to the local cli usage.

TODO:

• Check if setting just projectPath is enough, for example if a repo contains multiple tauri projects, or none.
• Check the docs and general behavior of projectPath
• Add support for reading json strings in the --config flag -> this may be outsourced to a second PR.

Edit: A few successful runs:
https://github.com/FabianLars/tauri-action-testbed/actions/runs/4665698961
https://github.com/FabianLars/tauri-action-testbed/actions/runs/4665905996

[FabianLars]

@lucasfernog 2 questions:

• What do you think about this PR's idea? Do you have any arguments to keep the configPath option? please consider that the option currently doesn't really work (at least not as it is documented which is partly my bad but it was also wrong before i reworded the readme)
• What are your thoughts about projectPath when github supports a working-dir option natively? I'm asking because the action and tauri itself use a different root for the --config option, of course this is an easy fix but the less custom handling the better imo

[lucasfernog]

The configPath input was meant for repositories that only have a frontend and only need the basic Tauri template to work (that's why we also have the option of running tauri init automatically). So since you're not commiting the Tauri template, we offer the option to use the tauri.conf.json file from another path.

I think this use case was never perfectly implemented and it's ok to slowly remove it. We'll probably implement this kind of thing with a different service.

About the projectPath thing: I think working-directory only works when running shell commands, and custom actions must implement an input for this.
@FabianLars

[FabianLars]

The configPath input was meant for repositories that only have a frontend and only need the basic Tauri template to work (that's why we also have the option of running tauri init automatically). So since you're not commiting the Tauri template, we offer the option to use the tauri.conf.json file from another path.

Yeah that doesn't work right now. I meant to fix it but thought it'd be way easier to just remove this option and let users use the normal --config option to overwrite the default one, this way it would be closer to "native tauri" making it at least easier to maintain for us, maybe even easier to use for some users.

About the projectPath thing: I think working-directory only works when running shell commands, and custom actions must implement an input for this.

Gonna check that but sounds about right 🤔