post new ecosystem imports to validator

[reedstrm]

Now that validator has an API for importing a book+exercises, when a new ecosystem is imported into tutor, go ahead and POST that to validator as well.

API: POST yaml file to: /import, example cli:

http --form --timeout 600 https://validator-dev.openstax.org/import file@new_book.yml

[carlycurran]

Tutor should post the file to response validator when we import a new YAML file

[nathanstitt]

@reedstrm do you have any suggestions on how @Brooke-Fail could test that the update occurred? I don't think the validator exposes what book version it's using anywhere 🤔

[Brooke-Fail]

I imported a new ecosystem and updated the book version, then updated the course offering to the newly imported book, waited 30 mins and I still didn't see the new book number on validator. I was verifying in staging using https://validator-staging.openstax.org/status. Validator v5.0.0 was deployed.

[nathanstitt]

Removing from release and moving to code so we can debug further

[Dantemss]

After a lot of confusion with the ecosystems I managed to check the most recent 10 or so ecosystems on staging.tutor.openstax.org and they all show up in https://validator-staging.openstax.org/status (the new ones seem to show up at the bottom of the list).

So please re-test when possible.

[Dantemss]

Something to watch out for is that if the same book uuid/version is imported twice, a second copy of it is not created in validator. So when testing you'll have to search the list to see if your entry is already there, not necessarily at the bottom.