[Audit FIx] remove extra settingName param from ElasticDAO events

[dmvt]

events MaxVotingLambdaChanged and ControllerChanged have a parameter 'bytes32 settingName' which I think is useless as the only place where these events are emitted are in function setMaxVotingLambda and function setController respectively.

Definition of Done

• MaxVotingLambdaChanged does not accept settingName
• ControllerChanges does not accept settingName