i18n Text Translations: partners and search

Files:

components	LearnTestimonyComponents	LearnComponents
components	Our Partners	OurPartners
components	Our PartnersCardContent	Our PartnersCardContent
components	Policies	PolicyPage
components	PriorityBillsCard	PriorityBillsCard
components	ProfileLink	ProfileLink
components	Search	BillHit
components	Search	BillSearch
components	Search	NoResults
components	Search	ResultCount
components	Search	SearchErrorBoundary
components	Search	service
components	Search	SortBy
components	Search	useRefinements
components	table	PaginationButton

• Move user-visible text from these section into json files in the public/locales/en folder; use the next-i18next 'useTranslation' hook to connect the text from the json files
• You'll decide how to group and name your text in a way that makes sense for your section by default, make separate json files following the structure of the project pages/folders, but feel free to diverge from that if needed.
• make sure to get titles, headers, buttons, labels, and alt text
• Put common words, labels, etc in the common.json file
• At this time, don’t worry about translating content on the files in the pages folder itself at this time, but you will need to update these files to include the json files you created.
• some pages may have already been extracted more or less into files next to or near the component files, usually with the same file name with 'content' on the end. That text needs to be moved as above, and it's up to you what to do with the content file.