feat(next): support document view conditions

[jessrynkar]

Introduces the ability to conditionally render document views. This way you can restrict access to entire views based on certain criteria, such as requesting user or data.

For example, you might want to limit access the /:id/api route to only certain roles.

To do this, use the new condition property in your edit view's config:

import type { CollectionConfig } from 'payload'

export const MyCollectionConfig: CollectionConfig = {
  // ...
  admin: {
    components: {
      views: {
        edit: {
          api: {
            condition: ({ req } ) => Boolean(req.user.roles.includes("admin"))
          }
        }
      }
    }
  }
}

[jacobsfletch]

This is looking good—and now that I think about it, we can also deprecate the hideAPIURL property at this point!

We used to render a link to the API endpoint directly on the edit view, but now that it's been given a dedicated page, view conditions should be used to control this instead. I don't think it makes a lot of sense to continue using this property.

[jacobsfletch]

It just dawned on me that we might want to control default views on a different property. This will be more future proof, as these features may not use views forever. For example Live Preview is actively being mounted to the /:id route. Let's talk about this.