Loosen ViewComponent invoke restrictions

[NTaylorMullen]

@rynowak and I talked a bit about this in person and I found it very unappealing how in today's world we don't provide a default signature for Invoke/InvokeAsync which makes building ViewComponents inconvenient.

Potential fixes to this could be allowing

Component.InvokeAsync("typeName", "methodName", myparams)

Or some derivative. Even possibly:

Component.Invoke<MyParamObject>("typeName", new MyParamObject(...))

Which would allow us to have a virtual Invoke/InvokeAsync signature.

Of course these are just ideas thrown around and neither may be the right solution to the problem. We should discuss making this API simpler and easier to get started with to prevent users from writing code that never gets invoked.

[rynowak]

Also interesting to bring back the idea of an expression-based syntax. We discussed this but stopped short of committing to build it.

@Component.Invoke<TagCloud>(cloud => cloud.ShowTags(count: 10))

[NTaylorMullen]

👍

[rynowak]

Or once we have @inject support..

@inject ViewComponent<TagCloud> Cloud

Cloud.Render(c => c.ShowTags(count: 10))

[rynowak]

Bumping this up because we had more discussion about it.

[rynowak]

Clearing triage per discussion at #3211