fix: use "price" in ecommerce data loader

[tecoholic]

Description

The Django Oscar upgrade of ecommerce changed the
item's price field from price_excl_tax to just price
causing the EcommerceApi data loader to fail.

This commit handled the exception and falls back to
the 'price' value.

Ref: openedx/ecommerce#4050

Additional information

The same as #4291.

Testing instructions

Reproduce Issue

1. Setup Tutor 18 (Redwood) dev env with the plugins ecommerce and discovery enabled
2. Clone course-discovery.
3. Add a tutor mount for the course-discovery.
4. Create a course or import the demo course.
5. Setup admin user for ecommerce and discovery
6. Add a course seat in http://ecommerce.local.edly.io:8130/courses/ for the test course
7. Run the following from Discovery Shell to set the ecommerce API url. NOTE: trying the same in Discovery admin fails due to URL validation.

   from course_discovery.apps.core.models import Partner
   p = Partner.objects.get(short_code="dev")
   p.ecommerce_api_url = "http://ecommerce:8130/api/v2/"
   p.save()
   

8. Run ./manage.py refresh_course_metadata --partner dev. It should fail with the KeyError price_excl_tax.

Testing the fix from PR

1. Checkout the PR branch
2. Run ./manage.py refresh_course_metadata --partner dev again. This time, it should run successfully.

[openedx-webhooks]

Thanks for the pull request, @tecoholic!

What's next?

Please work through the following steps to get your changes 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.

🔘 Let us know that your PR is ready for review:

Who will review my changes?

This repository is currently maintained by @openedx/course-discovery-admins. Tag them in a comment and let them know that your changes are ready for review.

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.

[tecoholic]

@AfaqShuaib09 Thanks for the suggestion. I have applied it to the PR.

[AfaqShuaib09]

Hey,

Don’t we need to update other places, like in this closed PR?
https://github.com/openedx/course-discovery/pull/4291/files

i.e;, in update_entitlement and validate_stockrecord methods?

[tecoholic]

@AfaqShuaib09 I raised the with the fix for just the one place where I encountered an error. If other functions also need to be updated, I can do that. But I am not sure what those functions do. So, anyone can confirm those functions need to be updated, I can recreate update the PR accordingly.

[Ali-D-Akbar]

@AfaqShuaib09 I raised the with the fix for just the one place where I encountered an error. If other functions also need to be updated, I can do that. But I am not sure what those functions do. So, anyone can confirm those functions need to be updated, I can recreate update the PR accordingly.

Hi there! I do agree with Afaq since this field was previously added in the aforementioned closed PR. Also, I believe adding it in update_entitlement and validate_stockrecord is also the right way since both of these functions are used in EcommerceApi Data Loader and having the correct price value should be the right thing else it will result in failure again.

[tecoholic]

@AfaqShuaib09 @Ali-D-Akbar Hi, thanks for confirming. I have updated the references in the mentioned functions and the mock data as well. Can you kindly review?

Note: All the CI checks for Python 3.8 seems to be failing due to a setuptools error. I want to highlight that course-discovery tutor template for redwood uses Python 3.12. So we can safely disregard the 3.8 failures.