Don't throw when SqlServer ValueGenerationStrategy is configured on an incompatible property by a convention

[AndriySvyryd]

Fixes #7208

[ajcvickers]

I want to see if my understanding of this issue is correct:

• We don't have any conventions that do this
• If somebody writes a convention to do this, then that convention would be wrong because it is not valid to have this strategy set on an incompatible property

Would it therefore not be better to continue to issue the error? Or are there some cases where it the error is being issued erroneously and it is in fact valid to have the strategy set on the property.

[ajcvickers]

Talked to @AndriySvyryd and I now understand why this makes sense given the way these APIs have been designed. So signing off. But I'm still concerned that this seems like code that will never actually be needed, so filed #7410 to cover that.