ix: remove force

[sakulstra]

I don't see a good reason on why one would want to rebuld via --force ignoring all caches.
In bigger foundry projects this can take a decent amount of time.
Therefore I'm removing the "force" - if you have strong feelings about keeping it i guess it could be an option to enable/disable via cli flag.

[kartojal]

Unfornately if you don't use --force and there is no changes, forge will not generate the build-info artifacts.

$ forge build --build-info
[⠔] Compiling...
No files changed, compilation skipped
Compilation successful

[catapulta-verify] Exiting main handler, error:
ENOENT: No such file or directory
   path: "out/build-info"
 syscall: "open"
   errno: -2

[kartojal]

i could add an "skip --force" param, but must only be used if you already did --build-info --force before, to prevent multiple forced builds

[sakulstra]

I think it would be better to do it conditionally if the required files don't yet exist (providing a flag seems like an unnecessary error surface).

If sth like foundry-rs/foundry#6278 would exist, potentially rebuilding via --force could be less painful.

[kartojal]

i will implement your idea to detect if build-info exists to skip the --force build in consequent verifications

[sakulstra]

Seems like the original issue holding this back was resolved in foundry-rs/foundry#7347