The APOD API no longer appears to provide a CORS-friendly way of loading the image itself

Previously, based on older issues, there was a suffix path /direct that could appended to the APOD API which would return the image itself, but with CORS allow-origin headers present. It seems to be the below issue referenced by @amygoodchild in a comment back in January.

I have searched but am unable to find an alternative endpoint in any documentation which provides that ability. Was this feature removed? Could it be enabled again? Or perhaps the APOD webserver where the images are hosted could be updated to add CORS headers when serving image file types from within the paths used for serving APOD images?

Mozilla provides details on the process here:
https://developer.mozilla.org/en-US/docs/Web/HTML/CORS_enabled_image

The original referenced post:

I'm having the same issue. The direct URL is broken and the other one doesn't allow me to use the image url in my code due to a CORS error. Any chance of getting this looked again? Thanks so much!

Originally posted by @amygoodchild in https://github.com/nasa/api-docs/issues/37#issuecomment-759621330

Start by reviewing the APOD API behavior around the documented or previously used /direct suffix and compare it with the APOD image-hosting paths. Use the linked Mozilla CORS guidance to identify the required response behavior; done means a documented, working CORS-friendly way to load APOD images, with the endpoint or hosting change confirmed.