----
First I've removed support for setting up sentry via the log module. It's insufficient. You now *must* set up sentry integration
through the sentry module. This now requires that you provide a release version which will be provided to sentry. This is better
because it also will increase the context data sentry gets about our user accounts.
So, where you had
sepiida.log.setup_logging(sentry_dsn)
you should now do
sepiida.sentry.add_sentry_support(app, sentry_dsn, version)
The sentry module also includes a new function, handle_reverse_proxy, which can be used when operating behind an nginx proxy
to get the correct origin IP information to sentry. You should add a call to this function to the wsgihandle.py module in your
client application if you use nginx as a reverse proxy to something like uwsgi
Further, resource_name is now required whenever creating or updating permissions. This has ripple effects through the permission fixture in tests as
well as regular code that is just creating permissions. Any time you call permission.create or permission.update you should include a
resource_name. This value is only meaningful to the client application - sepiida expects no special meaning and permits any string value
Finally, when calling update_filters sepiida will now look at your current filters and start optimizing the request to pao based on those
filters. For example, if you are already filtering down to a single uuid, sepiida will now only request from pao whether or not you have access
on that specific resource. It also only requests the fields that it needs so it doesn't immediately throw away a bunch of data. This
should not effect anything about correctness or the API for update_filters, it should only effect performance, but it's a big change so worth mentioning