Omitting primitive equality breaks interface generation

[SteveDunn]

Describe the bug

You can omit primitive equality generation with:

[assembly: VogenDefaults(primitiveEqualityGeneration: PrimitiveEqualityGeneration.Omit)];

But this conflicts with other generated code, in particular the generation of the IVogen<> interface. To demonstrate, this cominbation causes compilation errors as IVogen expects implementers to have equality to the primitive:

[assembly: VogenDefaults(
  primitiveEqualityGeneration: PrimitiveEqualityGeneration.Omit,
  staticAbstractsGeneration: StaticAbstractsGeneration.MostCommon | StaticAbstractsGeneration.InstanceMethodsAndProperties)]

... causes...
Error CS0535 : 'ToDoItemId' does not implement interface member 'IVogen<ToDoItemId, int>.operator ==(ToDoItemId, int)'

### Steps to reproduce

Omit equality to primitive generation, and specify IVogen interface generation.

### Expected behaviour

For `IVogen<>` to not declare primitive equality methods and operators.

[SteveDunn]

The trouble with this is that the configuration for primitiveEqualityGeneration can be specified at the global level and at the local (instance) level.
The local level overrides the global level.
So, when generating the interface, it looks at the global level and will generate/omit based on that. This means that if anything differs between global/local config, it will result in either compilation errors saying that a type does not implement the equality operators, or, the interface won't have the equality operators when a user would expect it to have them.
I don't think there's a solution for this other than to document that the global config is always used when generating the interface. I think this is a fair and obvious requirement.