entangled sync does not have `--force`

[jerivl]

Describe the bug
entangled sync does not have a --force flag despite an error message being thrown

To Reproduce

$> entangled sync
[21:00:10] INFO     Welcome to Entangled v2.4.2!
           INFO     Tangling.
           INFO     create `test.nix`
           WARNING  `test.nix` not managed by Entangled
           ERROR    conflicts found, breaking off (use `--force` to run anyway)
$> entangled sync --force
[20:59:57] INFO     Welcome to Entangled v2.4.2!                                                                                                                              
  Usage: entangled sync [OPTIONS]                                                                                              
                                                                                                                               
 Try 'entangled sync --help' for help                                                                                          
╭─ Error ─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╮
│ No such option: --force                                                                                                     │
╰─────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
                                        

Expected behavior

$> entangled sync
[21:00:10] INFO     Welcome to Entangled v2.4.2!
           INFO     Tangling.
           INFO     create `test.nix`
           WARNING  `test.nix` not managed by Entangled
           ERROR    conflicts found, breaking off (use `--force` to run anyway)
$> entangled sync --force
[21:00:10] INFO     Welcome to Entangled v2.4.2!
           INFO     Tangling.
           INFO     create `test.nix`
           WARNING  `test.nix` not managed by Entangled           
           WARNING  conflicts found, but continuing anyway

[EmiliaJarochowska]

The same complaint on the logic of the warning applies to entangled watch

[jhidding]

I'm a bit scared of having a --force on a command that is not deterministic. When you run sync or watch, you don't know in advance what action it will perform. Often, the case is that both tangle and stitch need to be run to make sure everything is in sync. We should change the error message to be smarter about the context in which the error is raised.

As a more comprehensive solution, I think it is better to reintroduce the feature to have the user confirm transactions through dialogue. This used to be in the Haskell version of Entangled but I never bothered to reimplement it in the Python version.