Enhance development feedback with warnings & notifications for hidden or disabled features

[Paul-Bob]

This issue depends on a notification system, as specified in:

• Notifications #2121
• Add a way to communicate with the developer in dev mode #2130

This issue tracks a list of warnings to be implemented during development, ensuring developers receive clear feedback rather than silently hiding or disabling features.

• Policies

  • When something is hidden or unauthorized, ensure developers receive clear feedback during development. Currently, adding field :users, as: :has_many does not render the field unless the corresponding def view_users? = true is added to the policy. Without this feedback, it can be difficult for developers unfamiliar with Avo to understand what’s happening.

• Not standalone Actions

  • When first working with actions, most developers expect them to work immediately. If they are unaware of the standalone setting, they may not understand why an action does not run or appears disabled. Providing feedback, such as a pop-up message saying "Select records to run this action" for non-standalone actions, could help clarify this behavior.

• Pro / Advanced options

  • When attempting to access features not included in the current plan, providing a clear message would be helpful. For example, if a developer on the Pro or Community plan adds filterable: true to a field, there should be feedback like "Dynamic filters are a part of the Advanced plan. Click here to upgrade." This would prevent confusion and improve the developer experience.

  • Here is a list to track these options:

    • filterable (Dynamic Filters)
    • searchable