Add missing error types to raise_error matcher

[manicmaniac]

Resolve the following warning on bundle exec rspec spec/lib/danger/request_sources/bitbucket_cloud_api_spec.rb.

WARNING: Using the `raise_error` matcher without providing a specific error or
message risks false positives, since `raise_error` will match when Ruby raises a
`NoMethodError`, `NameError` or `ArgumentError`, potentially allowing the
expectation to pass without even executing the method you are intending to call.
Actual error raised was #<WebMock::NetConnectNotAllowedError: Real HTTP
connections are disabled. Unregistered request: GET h... => 200, :body => "",
:headers => {})

============================================================>. Instead consider
providing a specific error class or message. This message can be suppressed by
setting: `RSpec::Expectations.configuration.on_potential_false_positives =
:nothing`. Called from
/Users/rito/Projects/danger/danger/spec/lib/danger/request_sources/bitbucket_cloud_api_spec.rb:104:in
`block (3 levels) in <top (required)>'.

[orta]

Thanks!