NetApp disable nfs v4.0 for new share servers

[Carthaca]

this has been the default for ONTAP 9.7 and 9.8 and we mistakenly
relied on that it would stay that way in
3503a19

But since ONTAP 9.9.1 the default is to enable nfsv40 again.

Now making the disablement explicit, since we now have a proper way to
distinguish between options that should be set on create and those
that should be set on update, too.

Change-Id: I39e2da2c3393ec95312c09a608a997a29981a471

[Carthaca]

This is more a nice-to-have for the flexgroup setup (since they said they will anyhow mount with v4.1)

[chuan137]

sth to follow up when Maurice back from vacation

1. why it's safe to update nfs3 and nfs41, shouldn't be the same logic applying to nfs40? i.e. allowed protols are configured on a new vserver, but never modify them, to avoid disruption to connected clients
2. with 'create' method, it would be more consistent to apply the nfs3 and nfs41 setttings together with nfs40. It works for us now because they are enabled by default, which aligns with our desired configuration.

[Carthaca]

sth to follow up when Maurice back from vacation

1. why it's safe to update nfs3 and nfs41, shouldn't be the same logic applying to nfs40? i.e. allowed protols are configured on a new vserver, but never modify them, to avoid disruption to connected clients
2. with 'create' method, it would be more consistent to apply the nfs3 and nfs41 setttings together with nfs40. It works for us now because they are enabled by default, which aligns with our desired configuration.

I fully agree, same logic should be applied for other protocol versions