[Tokens] Update css-library to 0.16.0 to get feedback tokens

[narin]

Description of Change

Updated css-library to 0.16.0 to grab 6 color tokens we had them add:

Primitive

• uswds-system-color-green-cool-vivid-30
• uswds-system-color-gold-vivid-40

Semantic

• vads-color-feedback-foregound-success-on-dark: uswds-system-color-green-cool-vivid-30
• vads-color-feedback-foregound-warning-on-light: uswds-system-color-gold-vivid-40
• vads-color-feedback-foregound-success-on-light: uswds-system-color-green-cool-vivid-50
• vads-color-feedback-foregound-warning-on-dark: uswds-system-color-gold-vivid-30

Also, VADS web team added their own font tokens in one of the recent versions, some of which conflict with our font tokens. I've added a filter to ignore web font tokens since there is no crossover for fonts between web and mobile.

Testing Packages

• 0.20.1-alpha.0

Screenshots/Video

Testing

• Tested on iOS
• Tested on Android
• Tested on Web

PR Checklist

Code reviewer validation:

• General
  • PR is linked to ticket(s)
  • PR has changelog label applied if it's to be included in the changelog
  • Acceptance criteria:
    • All satisfied or
    • Documented reason for not being performed or
    • Split to separate ticket and ticket is linked by relevant AC(s)
  • Above PR sections adequately filled out
  • If any breaking changes, in accordance with the pre-1.0.0 versioning guidelines: a CU ticket has been created for the VA Mobile App detailing necessary adjustments with the package version that will be published by this ticket
• Code
  • Tests are included if appropriate (or split to separate ticket)
  • New functions have proper TSDoc annotations

Publish

If changes warrant a new version per the versioning guidelines and the PR is approved and ready to merge:

• Merge main into branch
• Merge branch to main
• Verify that Check Component Integrations workflow ran successfully
• Publish new version after merging

[TimRoe]

Not sure if there's another way without digging at all, but just noting it feels weird to have a general filter that needs to be applied to all files that didn't previously have a filter to get rid of the vads-fonts.

[narin]

There doesn't seem to be a way to apply filters to an entire platform or transform group, but style-dictionary 4.0 introduces preprocessors which might be able to clean this up. Created #604 to follow up on it after we update to 4.0.

[TimRoe]

Approving since nothing necessarily needs to change, but have some comments/suggestions.

Also noting it's not linked to a ticket (is it supposed to be just to the same ticket as VADS?).