Combine scale-info feature into codec, and wire it through ethereum-types

[JoshOrndorff]

@sorpaas @ascjones

[ascjones]

This reminds me, now that we have scale-info 1.0 and it is integrated into substrate, we should probably:

• Tighten up the the requirement to 1,0
• Consider merging the scale-info feature into the codec feature: if you want one you get both.

inprogress

[JoshOrndorff]

Okay, this is ready for review.

[ordian]

This reminds me, now that we have scale-info 1.0 and it is integrated into substrate, we should probably:

* Tighten up the the requirement to `1,0`

* Consider merging the `scale-info` feature into the `codec` feature: if you want one you get both.

That would technically make this change breaking, because scale-info now doesn't imply codec feature and we drop compatibility with 0.9.

[JoshOrndorff]

Currently, I've applied @ascjones suggestions to use 1.0 and combine it all into the codec feature. Shall I:

1. Keep it that way and bump crate versions here as necessary (I guess this would be minor bump where the functionality was only added major where the scale-info trait was removed?
2. Go back to the less invasive approach of introducing a separate scale-info trait in each crate.

[ordian]

I would suggest reverting the changes for primitive-types and keeping everything else as is (modulo primitive-types/scale-info feature activation).

[JoshOrndorff]

@ordian I believe I've done as you asked. Can you please review it again?

[JoshOrndorff]

Thanks for the review and merge everyone! I'd like this change to trickle down to frontier in time for Sub0 conference on October 14th if possible. What would it take to get a release of ethereum-types published?

[ordian]

opened #594, will publish it soon