Update ValidateListResourceConfig to validate include_resource and limit

[stephybun]

Description

Updates the proto definitions for 5 and 6 to validate include_resource and limit

Rollback Plan

• If a change needs to be reverted, we will roll out an update to the code within 7 days.

Changes to Security Controls

None

[bbasata]

[bbasata]

This was my first look at the updated proto files, so the DynamicValues for primitive-or-unknown in the protocol surprised me. It feels like a rare example/precedent – a DynamicValue typically represents a value with a provider-defined schema type.

I do recall the discussion of allowing expressions in config, so this may indeed be necessary. My one thought here is to consider how to simplify access to these fields in Framework – and possibly plugin-go too – for the provider developer.