Expose maven_export

[sacsar]

This PR makes some of the changes referenced in #855. I am not convinced this is the best possible API to expose -- I basically made the minimal changes -- in particular, I think the lib_name parameter is a bit awkward (maybe it should be dep or library?) and I'm pretty sure the docstring could be further refined.

NOTE: I did run the doc script, but it resulted in no changes.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[shs96c]

LGTM. Thanks for keeping the changes minimal. I'm curious to know what you think a better API would be, but we can discuss that on Slack :)

[shs96c]

@sacsar, before I can merge this PR, could you please sign the CLA? This comment contains a link to get you to the form you need to fill in.

Once the checks are green, I'll be happy to merge this PR.

[sacsar]

Will do -- I'm trying to figure out if I should sign the CLA as myself or as my employer.

[shs96c]

Please take this with a large dose of "I am not a lawyer".

It depends on your employment contract with your employer. If they've made a land-grab for any IP you create while employed by them (even in your spare time), then I think it's best to sign the corp CLA. If you're working independently, and there's no clause in your employment contract attempting to lay claim to this PR, then signing as an individual is fine.

[sacsar]

We decided that this is sufficiently close to my actual work that we should sign the "corporate CLA", which has been completed. I think we're now just in processing limbo, as I've updated the commit to have my work email address.