U-4293 Catalog and Policies v3 tweaks

[PetrHeinz]

The was an issue with the computed optional metadata value fields item_id, email, and name:

When you saved {type:"User",email:"foo@example.com"}, you would get item_id and name in the response, saving it into state.
This extra state would get saved.
When chasing that value to {type:"String",value:"my string"}, the previously saved item_id and name would be send alongside.

I tried to overcome this issue, but haven't found a way to distinguish the computed optional values from human-configured values.

My solution here is to remove the Computed flag from these fields, and prevent saving the values from API. If this wasn't prevented, the plan after applying would always include the attempt to remove the item_id and name from the value, making the plan unstable.

Fixes both #136 and #137

[adikus]

Thanks! A bit of a shame that this is necessary 🙈

[PetrHeinz]

@adikus I was trying to avoid it, but haven't found a way. In newer version of Terraform there are some features that might be helpful, but that would mean dropping support for a lot of previous versions, and I didn't want ot commit to that.