The situation is significantly more nuanced than you understand.  It is clear you have not fully read and understood the T&C.  Please go back and re-read them in its entirety.  Quoting five words does not indicate that you have read the 2,600 the terms contain.

Next, please review how the Street View product works.  Does anything in there say "paved"?  Of course not.  The imagery does not contain that data.  Nor can we conclusively decide that this way is indeed paved from an image alone.  For that we need to combine with other sources, such as the local transportation authority, to confirm the different surfaces that they use for protected bikeways.  In this case, that is Portland Bureau of Transportation (PBOT), and PBOT uses green-tinted concrete to denote pathways used exclusively for cyclists.  None of that data is contained in any Google product.

If this changeset had used Google's imagery to infer the shape of the lane to create or edit it, you would be right, that is a clear cut violation of the terms.  However no data from any Google product has been directly used to create this changeset.  Your blanket statements of "anything that says Google is not allowed" is misleading and misinformed.

Finally, you have exhibited a gross misunderstanding of how the terms are applied.  If a contributor violates the terms, OSM is not a party to the violation.  Further, this is not a "test" of the lawyers.  This is real map data that your fellow humans depend on.