Add icon name mapping to va-icon ESLint migration script

[jamigibbs]

Description

Now that we have the Font Awesome names mapped to a USWDS name, we'd like to update the ESLint migration script to automatically fill in the mapping name to the icon prop.

We might be able to do something similar to like what was done for mapping new utility classes.

References

• Add Font Awesome to va-icon migration rule veteran-facing-services-tools#1025
• Name mapping chart

Tasks

• update the prefer-icon-component migration script so that the mapped USWDS icon name auto-populates

Acceptance Criteria

• given a provided Font Awesome class name, the mapped USWDS icon name populates for the icon prop in the va-icon migration script

[caw310]

Hey team! Please add your planning poker estimate with Zenhub @Andrew565 @ataker @harshil1793 @it-harrison @jamigibbs @micahchiang @nickjg231 @powellkerry @rmessina1010 @rsmithadhoc

[Andrew565]

Previous (Font-awesome) and current (USWDS) icon names as found on the design.va.gov site are accessible in yml format here: https://github.com/department-of-veterans-affairs/vets-design-system-documentation/blob/2797f1d4310b81227f52489036324e085dbf6744/src/_data/icons.yml