Exclude original_data field from PartialEq comparison

[Mr-Leshiy]

As original_data is not required to be set, used/initialised only in limited number of cases.
So to be still be consistent in comparison operation, I am suggesting to exclude original_data field from comparing implementation.
As a result it eliminates inconvenience to alway keep this field either empty or initialised to be able to properly compare two ProtectedHeaders instances at this moment.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[atezet]

Could this PR be considered? I think it makes a lot of sense to ignore original_data when comparing ProtectedHeaders. I ran into this when testing whether writing then reading it from a database would still result in the original object.

[daviddrysdale]

This PR cannot be considered without a CLA from the author.

[atezet]

@Mr-Leshiy would you be willing to sign the CLA?