Create arch-bom tickets for 2U specific DEPR follow-up

[robrap]

AC:

• Create follow-up tickets

The following are DEPR tickets that have 2U-specific follow-up with various deadlines that require our own ticketing/tracking. This ticket is for creating the appropriate tickets as-needed.

• [DEPR]: Asset processing in Paver openedx/edx-platform#31895
  • [DEPR-2U] Paver #679
• [DEPR]: Paver openedx/edx-platform#34467
  • [DEPR-2U] Paver #680
• [DEPR]: Phase out edx-configuration openedx/public-engineering#51
  • Clone configuration repository into the edx organization #622
• [DEPR] Devstack openedx/public-engineering#247
  • [DEPR-2U] [Discovery] How do we want to handle devstack configuration without devstack.py files? #588
• [DEPR]: testeng-ci openedx/public-engineering#265
  • [DEPR-2U] testeng-ci #681
• [DEPR]: Dockerfiles and Docker images openedx/public-engineering#263
  • [DEPR-2U] [Discovery] How do we build devstack images post devstack-deprecation? #587

[robrap]

FYI: @dianakhuang: If you want to pick this up at some point.

[robrap]

@feanil: What is your plan for getting these individual DEPRs on the board and prioritized in place of this ticket? Thanks.

[robrap]

Note that openedx/public-engineering#265 was just proposed, and may require review by 2U to understand if there is any impact to working off the archived repo, or any other 2U-specific changes required.

UPDATE: I didn't realize that I had already added this ticket above for [DEPR]: testeng-ci #265, and that Kyle thinks it will not be a time sensitive change for 2U, according to this comment.