Change plugin prefix to not conflict with Bugbear

[tylerwince]

Change plugin prefix to not conflict with Bugbear

[myii]

@tylerwince @ambv I've made a further comment at PyCQA/flake8-bugbear#37. I'm quoting the salient points below:

The conflict is not with flake8-bandit but rather with openstack/bandit

There are two projects that are involved here:

1. https://github.com/openstack/bandit

   1. Project started on 16 July 2014
   2. This is the main project, where the conflicts are arising

2. https://github.com/tylerwince/flake8-bandit

   1. Project started on 29 Oct 2017
   2. However, this is just a wrapper around bandit
   3. They have no control over the error codes that are supplied by bandit

The OpenStack Bandit project has been using B30x codes for a few years as well

Taking B301 as the earliest example in both projects:

1. Bandit: openstack-archive/bandit@c364408

   1. This commit was made on 22 Jan 2016

2. Bugbear: PyCQA/flake8-bugbear@0fb7d8d

   1. This commit was made on 8 Jun 2016

[tylerwince]

Thanks @myii and @ambv.

Some comments I made on issue at PyCQA/flake8-bugbear#37 and reposting here to keep track of things:

We could always handle this internally in flake8-bandit. Definitely not a long term solution but a workaround until we can figure out which codes to be used by each project.

What are the thoughts around flake8-bandit changing the openstack/bandit code to be S30x for the time being? (quick look and it doesn't appear any other plugins are using S30x and S makes sense for "security")

Is anyone using flake8-bandit and comparing those results to the openstack/bandit cli output? That is the only time I could see this causing an issue as the codes won't match up

I've opened up an issue with openstack/bandit to see if we can pull them into the discussion here: https://bugs.launchpad.net/bandit/+bug/1759643

[tylerwince]

This have been closed. Please see the final discussion here:
PyCQA/flake8-bugbear#37