Improve the dev experience when a user doesn't apply an interactive render mode to a component that requires interactivity

Rendering components statically by default with no user feedback that interactive features won’t work is a major usability issue right now with Blazor. It’s not currently an error to render an interactive component statically, because interactive components are often prerendered statically. But accidentally rendering a component statically when you wanted it to be interactive is common. We should think about how we can help users out with this issue.