ci: disable auto dependency upgrades

[samuelallan72]

Description

We're no longer maintaining this, so we don't want to deal with the automated dependency upgrade PRs.

Supporting information

Ref: #482 (comment)

Private-ref: https://tasks.opencraft.com/browse/SE-6622

Testing instructions

• verify this is what we want
• verify this correctly removes all references to the auto dep updates

Author concerns

Do we want to just archive this repo completely, rather than removing this? If we're not maintaining this any more, archiving is probably the way to go. cc @bradenmacdonald

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 45.04%. Comparing base (b89d041) to head (2308863).

Additional details and impacted files

@@           Coverage Diff           @@
##           master     #483   +/-   ##
=======================================
  Coverage   45.04%   45.04%           
=======================================
  Files          40       40           
  Lines        3303     3303           
  Branches      401      401           
=======================================
  Hits         1488     1488           
  Misses       1768     1768           
  Partials       47       47           

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

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.

[Agrendalath]

@xitij2000, can we archive this repo? If yes, we can probably close this PR.

cc: @samuelallan72

[xitij2000]

@Agrendalath Not yet, we are still trying to work on a replacement.

[samuelallan72]

@xitij2000 does the readme warning need updating? :

Problem Builder is no longer being developed by OpenCraft. It will be supported with compatibility and security fixes till the Ulmo release, after which this repository will be stop receiving further updates and eventually be archived.

Are we planning to maintain this until we find a replacement? Did I hear that this will stop working altogether in a future openedx-platform release?

[xitij2000]

@samuelallan72 Yes, till we properly deprecate this and have a replacement, we need to maintain it.