refactor: replace use of mustache templates with edx-utils template

[navinkarkera]

Also removes underscore-min.js file which was unused

[openedx-webhooks]

Thanks for the pull request, @navinkarkera!

This repository is currently maintained by @navinkarkera.

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.

[navinkarkera]

@farhan Could you please review these changes?

[farhan]

@farhan Could you please review these changes?

Sure, let me prioritize it.

[farhan]

Very good work overall in removing legacy code.

But it will be great if we could directly update the template library to Django Template Library rather than to Mako templates, because we have already parted ways with Mako templates and shifting the code to Django templates library.

ADR:
https://github.com/openedx/open-edx-proposals/blob/ba75a70d7b062426403667822978f101d71fce2d/oeps/best-practices/oep-0067/decisions/frontend/0005-django-templates.rst#L24

[itsjeyd]

@navinkarkera Friendly nudge to follow up on review feedback here.

[navinkarkera]

@itsjeyd Thanks for the reminder.

@farhan Thanks for reviewing this, I'll address your feedback soon (maybe next week).

[navinkarkera]

Update: Sorry, could not find time to work on this yet. I'll try to get it done next week.

[navinkarkera]

@farhan We are actually not using mako templates in this repo, the mako like syntax is used by edx.HtmlUtils.template but it has no relation to mako, instead it makes use of lodash.template.

I removed mako from requirements here: a58ec8b

[ttqureshi]

I've reviewed and tested the changes. LGTM ✔️

cc: @farhan