Consistently implement equals and hashCode in ResourceMetadata subclasses

Currently ResourceMetadata subclasses don't use all fields in their equals and hashCode methods. This can make sense given the nature of those objects, but can lead to unmet expectations for some users.

There has to be a statement of whether or not fields such as the metadata, tags, and so should be considered in equals/hashCode.