Deploy OpenAPI with Github Actions

[dmohns]

Brief summary of the change made

This PR implements a few improvements around our OpenAPI docs (and their generation)

• Fix scribe:generate to use actual authentication. Previously most auto generated entries simply showed un-authenticated error
  

  This now works much better:

  

• Fix some errors thrown related to wrong path of response files

• Remove openapi.yaml from version control. It's should be treated like a generated artifact. Update the docs deployment pipeline to generate it on the fly.

Note

The motivation for this change is to generally improve and overhaul our API documentation.
As we need to share it with external parties and collaborateurs like Vodacom.

Are there any other side effects of this change that we should be aware of?

Describe how you tested your changes?

Pull Request checklist

Please confirm you have completed any of the necessary steps below.

• Meaningful Pull Request title and description
• Changes tested as described above
• Added appropriate documentation for the change.
• Created GitHub issues for any relevant followup/future enhancements if appropriate.

[beesaferoot]

Nice! This will be useful as an API deference. I left some minor comments

[beesaferoot]

I'm curious why we need an elaborate db setup like this?

[dmohns]

Scribe has a lot of different ways to gather information about the API's. It can get this information from PHPDoc, reponsefiles or even types in some cases. Most of our routes do not have any of these. As a fallback, scribe will simply call the endpoint and use the response it gets.

To use this, we basically have to run php artisan scribe:generate in a demo setup.

[beesaferoot]

This looks great. Already seeing how this make things easier to segment on the docs for subsequent PR.

[beesaferoot]

MicroPowerManager supported different typo here i believe you meant MicroPowerManager supports different

[dmohns]

Superseded by: #1398