Provide more context to fields

A common issue for users of Administrate is that fields do not receive enough context. The most typical use case is that they cannot modify the configuration of a field depending on the current user: hiding/showing the field, showing different select options, etc.

These are some relevant issues, marked https://github.com/thoughtbot/administrate/labels/fields-context. Some of these refer directly to the lack of context, others are a bit more indirect but still related:

• https://github.com/thoughtbot/administrate/issues/1342
• https://github.com/thoughtbot/administrate/issues/1586
• https://github.com/thoughtbot/administrate/issues/1862
• https://github.com/thoughtbot/administrate/issues/1988
• https://github.com/thoughtbot/administrate/issues/2060

My initial intuition would be to pass the current controller down to fields, so that it can be used as provider of context. This can be passed in turn to the call-able that some options take, as well to new options such as hide_if or something like that.

Start by reviewing the linked fields-context issues to identify the recurring requirements around current-user access, conditional visibility, and dynamic select options. Then trace how fields receive configuration and how callable options are evaluated; done should provide a decided, documented context mechanism that supports these use cases.