provider/aws: fixing some logic issues with the aws-instance resource

1. The schema contained a few fields that where not marked as `computed`, while they were updated inside the resource.

2. While updating the `volume_size` it was doing so with a `string`, but in the schema this field is set as `int`.

3. The set func for calculating the hashes for the `block` set items, also used computed values to calculate the hash. As these values will not be in the config, but only in the state, this will always show as a diff. The solution is to only use the fields that aren’t computed in order to get consistent hashes.

These where all issues before, but weren’t visible as such. All should be good again now.