add/run/import-url: don't use -f as --file

[efiop]

If anything, -f is closer to --force than to --file. So let's set
this straight.

• ❗ I have followed the Contributing to DVC checklist.

• 📖 If this PR requires documentation updates, I have created a separate PR (or issue, at least) in dvc.org and linked it here. If the CLI API is changed, I have updated tab completion scripts.

iterative/dvc.org#1255 iterative/dvc.org/issues/1426

• ❌ I will check DeepSource, CodeClimate, and other sanity checks below. (We consider them recommendatory and don't expect everything to be addressed. Please fix things that actually improve code or fix bugs.)

Thank you for the contribution - we'll try to review it as soon as possible. 🙏

[jorgeorpinel]

Hi. I see a checkbox was added for this in iterative/dvc.org/issues/1255, thanks. But that's not really a catch all epic for every change from now on 😋

I may be wrong but this doesn't sound like a 1.0-specific change to me, can we open a separate docs issue or PR instead, please?

[efiop]

@jorgeorpinel it is used all over the docs and I have no idea what to change there because of all of the 1.0 conflicting PRs hanging that affect all of the docs that I need to change. So I've added it to the epic.

[jorgeorpinel]

Please open an issue and link to the core PR when submitting a PR is not possible. That's totally fine. Done: iterative/dvc.org/issues/1426

[efiop]

@jorgeorpinel It was added to the epic get rid of -f in add/run/import(-url) per iterative/dvc#4004 and iterative/dvc#4011, you can see it in the history of changes, but you've deleted it in the past two days.

[jorgeorpinel]

I extracted it into iterative/dvc.org#1426 like I just mentioned. Thanks