Add missing OBJECT_VALIDATION attributes to objects

[Jakuje]

Description

The object validation flags were somehow properly checked in the session for the validation state and missing flags on objects were ignored as they were computed on the fly. But these attributes could never make it to the user as even if they would be set during key generation, they were stripped while saving the attributes to the database (and never set for imported keys).

Fixes also bunch of related issues.

Built on top of #314 to have the build working.

Checklist

• Test suite updated with functionality tests
• Test suite updated with negative tests
• Rustdoc string were added or updated
• [~] CHANGELOG and/or other documentation added or updated
• [~] This is not a code change

Reviewer's checklist:

• Any issues marked for closing are fully addressed
• There is a test suite reasonably covering new functionality or modifications
• This feature/change has adequate documentation added
• A changelog entry is added if the change is significant
• Code conform to coding style that today cannot yet be enforced via the check style test
• Commits have short titles and sensible text
• Doc string are properly updated

[simo5]

This will cause us to pay the price of key validation on each retrieval ... we may want/need to add some form of caching later...
But otherwise I think this is fine for now.

[Jakuje]

This will cause us to pay the price of key validation on each retrieval ... we may want/need to add some form of caching later... But otherwise I think this is fine for now.

The NSS code had e907d3e which basically considered any key in DB valid. I got to think about that only after implementing this change, but it might be also an option to set this attribute for really everything in the DB. But then we would need to be more precise to make sure we do not let in any non-fips objects :) So feel free to open a separate issue if you have some thoughts about this further.