support for CLIENT KILL MAXAGE

[atakavci]

Closes/Fixes #2726

added two overloads and use a filter object to avoid a breaking change.

[NickCraver]

Reviewed on the call today - in general, this pattern won't work due to the server-side API supporting n filters, we'd need to allow n of them ordered on the command. We'd either need to take a params here or more likely do a builder pattern for n filters. In a builder, returning itself, we could do things like making a method per filter that's very specific and only has the args needed for the 7 doced paths:

• CLIENT KILL ADDR ip:port
• CLIENT KILL LADDR ip:port
• CLIENT KILL ID client-id
• CLIENT KILL TYPE type
• CLIENT KILL USER username
• CLIENT KILL SKIPME yes/no
• CLIENT KILL MAXAGE maxage

This wouldn't be very dissimilar to the constructors you have now in terms of one-per, but we can make it intuitive and pit-of-success here for users to do the right thing. And we can make it write the message directly on the backend since it's in the base library. Picture for example:

IServer.ClientKillAsync(new ClientKillFilter().WithAddr(...).WithSkipMe(true));`

Thoughts?

[atakavci]

hey @NickCraver , sounds nice and clear ! please take a look with new commit.