feat: add Transifex config for freetextresponse translations

[irfanuddinahmad]

Summary

• Adds src/freetextresponse/.tx/config to wire freetextresponse into the openedx-translations pipeline
• The resource slug is xblocks-extra-freetextresponse, matching the pattern used by all other xblocks in this repo (e.g. xblocks-extra-sql-grader, xblocks-extra-submit-and-compare)
• No other changes needed: conf/locale/config.yaml already exists, and the Makefile auto-discovers freetextresponse via find src/ -mindepth 2 -maxdepth 2 -type d -name 'conf'

Closes #41 (together with a companion PR in openedx/openedx-translations adding the transifex.yml entry)

Merge sequence

1. Merge this PR (feat: add Transifex config for freetextresponse translations #45) — triggers extraction run, populates translations/xblocks-extra/freetextresponse/ in openedx-translations
2. Merge feat: add xblocks-extra/freetextresponse to translations pipeline openedx-translations#74373 — adds transifex.yml entry for xblocks-extra/freetextresponse
3. Verify Verify xblocks-extra translation coverage for free-text-response #42 — confirm new path has ≥ 37 locales (matches legacy xblock-free-text-response coverage)
4. Merge feat: remove legacy xblock-free-text-response translations openedx-translations#74375 — removes legacy xblock-free-text-response entries (resolves Remove legacy standalone xblock-free-text-response translations from openedx-translations #43)
5. Validate end-to-end translation flow for free-text-response in LMS #44 — manual LMS validation: run make pull_xblock_translations in lms-shell and confirm translated UI renders correctly

Test plan

• CI passes (lint + tests)
• Companion PR feat: add xblocks-extra/freetextresponse to translations pipeline openedx-translations#74373 is open and extract-translation-source-files workflow validates the entry

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 82.24%. Comparing base (4020699) to head (41fbe63).

Additional details and impacted files

@@           Coverage Diff           @@
##             main      #45   +/-   ##
=======================================
  Coverage   82.24%   82.24%           
=======================================
  Files          49       49           
  Lines        1425     1425           
  Branches      110      110           
=======================================
  Hits         1172     1172           
  Misses        221      221           
  Partials       32       32           

Flag	Coverage Δ
unittests	82.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[openedx-webhooks]

Thanks for the pull request, @irfanuddinahmad!

This repository is currently maintained by @openedx/axim-engineering.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[mphilbrick211]

Hi @openedx/axim-engineering - this is ready for review. Thanks!