What is the problem?

By our metrics naming convention, all units are anyway supposed to be appended to the metrics name. We shouldn't allow to specify this in the core backend.

cc @edoakes

Reproduction (REQUIRED)

Please provide a script that can be run to reproduce the issue. The script sh

$ semgrep -c p/python ../server/setup.py
semgrep: error: unrecognized arguments: -c

I get this almost every week 😅 Since nothing else uses -c we should be good to use it here, right? I assume it was originally -f cause it was used to pass a config file, but now most people pass shorthand or URLs instead of local files.

It's also probably a good idea to keep -f as a hidden al

I'm sorry if I missed this functionality, but CLI version hasn't it for sure (I saw the related code only in generate_code_examples.py). I guess it will be very useful to eliminate copy-paste phase, especially for large models.

Of course, piping is a solution, but not for development in Jupyter Notebook, for example.

We noticed that we have some common patterns for common conflicts/duplicate resolution in our monorepo across different binaries.
Like

  deploy_jar_rules=jar_rules(rules=[
    Duplicate('^BUILD', Duplicate.SKIP),
    Duplicate('^META-INF/ASL2.0', Duplicate.SKIP),
    Duplicate('^META-INF/INDEX.LIST', Duplicate.SKIP),
    Duplicate('^META-INF/io.netty.versions.properties', Duplicate.SKIP