Controls for the inclusion of the common attributes

This sorta goes with #286.

Since `macros` already auto include the common attributes in their documentation, it would be nice to have some controls over that.

For example
- a test rule might not actually support sharding, so while those attributes are _valid_, they have no meaning and can just result in clutter for someone trying to read the rule/macro attributes.
- likewise, things like `args` for a test rule might not really apply to running a test, so skipping those could be good.

Another potential options would be instead of adding controls for showing/hiding of things, to maybe present the common attributes differently. Maybe if while iterating over the attributes one could tell if it as a common one or rule/macro specific, the listing could be split into two, an initial table of the rule/macro specific attributes, and then second table of the common ones? Or maybe don't even list the common one in the table, but have the overview link them directly out to some common definitions document instead so the table developers read is only the rule/macro specific things?