feat: filter.createSubscription accept ShardParams

[vpavlin]

support request

Problem

It seems like filter.createSubscription accepts either pubsubTopic or SingleShardInfo - which in turn consists of ClusterId and shard

Would it make more sense to accept ShardingParams to make it more flexible?

Requiring SingleShardInfo forces me to get the shard from contentTopic before calling createSubscription, which seems unnecessary to be done by a user/dev.

But I might be missing the reasoning behind this choice:)

Proposed Solutions

Notes

[danisharora099]

Looks right to me. Good point. Thanks for flagging this @vpavlin

Looks like the filter API wasn't updated after we introduced autosharding. Moving to priority.

@adklempner are you happy to address this?

[weboko]

I agree with @vpavlin and I think better way would be to simplify as much as possible but also allow to make fine tuning.

For that I see we can do:

• make it accept contentTopic and map it to a shard;
• provide API for advanced users to set particular shard or other params;

Since I am touching this code in #1958 I might be able to address it there.

[danisharora099]

@weboko issue seems to be in the "done" column but still open -- I guess we can close it?