Validate inputs for subscription destinations #417
Description
We currently don't check for additionally set fields when processing an update to a subscription. When fields are set that are not used for an update (for example region on an SNS destination) the provider breaks after apply because its new state is inconsistent with its expected state.
We should validate these inputs up front, and throw an error when fields are set that are not expected by the destination.