Fix `component!` macro treatment of generic parameters

[robpatterson13]

Right now, the component! macro incorrect propagates generic parameters through to the component's instruction set, value set, and type set. We should either a) investigate the heuristics that other libraries use to decide which parameters should be propagated on macro expansion, or b) partially redesign the macro with generic parameter treatment in mind.

[robpatterson13]

Superceding component! macro with an attribute