fix: rewrite calcualtor tips to reflect the supported features

[ghassanmas]

Description and Related information

It replicates this PR: openedx/frontend-app-learning/pull/825 which
rewrite calcualtor tips since some tips are no longer relevant,
hence: #17368

Testing:

To be to test this change, here are the steps:

• Make sure there is a course with Show Calcutrator to true, follow this doc link for more details
• Go to the learning experience as shown (from the above link as well)**
• When clicking on i button the calculator instructions tips, should reflect the change of this PR. e.g., there should be no example of using T as constant...etc.

** You would need to make sure that you are interacting with the course through the old course experience, not using the learning MFE hence, it's already resolved for the learning MFE openedx/frontend-app-learning/pull/825.
Relative information about how enable use old courseware experience:

The courseware.use_legacy_frontend and course_home.course_home_use_legacy_frontend Waffle flags can be toggled on (either globally or per-course-run) in order to revert to the Legacy (LMS Django-rendered) courseware experience.
ref

[openedx-webhooks]

Thanks for the pull request, @ghassanmas! I've created OSPR-6481 to keep track of it in JIRA, where we prioritize reviews. Please note that it may take us up to several weeks or months to complete a review and merge your PR.

Feel free to add as much of the following information to the ticket as you can:

• supporting documentation
• Open edX discussion forum threads
• timeline information ("this must be merged by XX date", and why that is)
• partner information ("this is a course on edx.org")
• any other information that can help Product understand the context for the PR

All technical communication about the code itself will be done via the GitHub pull request interface. As a reminder, our process documentation is here.

Please let us know once your PR is ready for our review and all tests are green.

[ghassanmas]

This ready for review also this #29080 as well

[mariajgrimaldi]

Hi there @ghassanmas!

Can you add testing instructions to your cover letter? That would be helpful for others! 😄

[ghassanmas]

@mariajgrimaldi Just did wrote detailed instructions to test and provided more context as well. Let me know if you have any questions.

[natabene]

@ghassanmas Thank you for the contribution. I will line this up for our review.

[rgraber]

@ghassanmas it seems like quality checks are failing, please resolve and then I can rereview

[ghassanmas]

@rgraber I did ran the ./scripts/xss-commit-linter.sh locally and got 0 violation. But how am I suppose to fix it here? Am I suppose to push result file humm

[rgraber]

@rgraber I did ran the ./scripts/xss-commit-linter.sh locally and got 0 violation. But how am I suppose to fix it here? Am I suppose to push result file humm

I'll take a look once tests run again

[rgraber]

Apparently there is a known issue with this test. We are going to disable it since it's not really that valuable anymore. at that point i'll rerun the tests on this guy and hopefully that will be enough

[ghassanmas]

Alright, in other words the tests needs tests 😅

[rgraber]

LGTM

[openedx-webhooks]

@ghassanmas 🎉 Your pull request was merged! Please take a moment to answer a two question survey so we can improve your experience in the future.

[edx-pipeline-bot]

EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production.

[edx-pipeline-bot]

EdX Release Notice: This PR has been deployed to the production environment.