Migrate content from component to CMS solution

[Dale Sande]

Is your feature request related to a problem? Please describe.

The auro-input component contains in-component content to support various features. This element has also been updated to support a loc transition from English to Spanish.

auro-input/src/i18n.js

Lines 71 to 77 in eab7457

 export default function i18n(lang, requestedString) { 
   if (lang === 'es') { 
     return stringsES[requestedString]; 
   } 
  
   return stringsEN[requestedString]; 
 } 

Any updates to this content would require a developer to release updates.

Describe the solution you'd like

Update the content within the scope of this element to be pulled from the ContentStack CMS solution allowing for reuse, expanded loc support and easy access to content for content editors and UX writers.

Additional context

This issue DOES NOT expand the scope of language support or imply new feature development that will allow for automated expansion of languages. At current time, if a new language is requested, this would be a feature add to this component.

Exit criteria

This issue can be closed once all content contained within the element have been removed and all content is being requested from the CMS solution.

Current scope is to only support Spanish and English.