manfuacturing-server: add an export REST API

[runcom]

when a manufacturer initialises many devices it's either gonna have OVs in files or in the database. Since the manufacturer has to move these OVs to the device owner, it'd be handy to have an export functioinality that exports a tarball with all the OVs. We can start with just that and have an API that does only that and expand in the future if other, more complex, queries and functions are needed.

What we need could be:

• a REST API
• authentication
• ability to export all the OVs as a tarball

Questions:

• do we care about tarball size?
• what do we do with the OVs server-side? do we delete them? there's no delete API or mgmt solution right now anyway

[7flying]

FYI: Currently the fdo-owner-tool can export OVs from the DB and dump a specific one or all of them into a path.

So the internal DB export capability is already there, missing the API stuff.

[runcom]

awesome, I think we could easily add the api to the manufacturing server which re-uses code from the owner-tool then