Clarify license and rights statement in OAI

[joemull]

Describe the bug In the OAI feed, there is some ambiguity in how we display license and rights statement info.

In DC, the rights info pulls from license: https://github.com/BirkbeckCTP/janeway/blob/959d7ddf5eed21aa02fc80bc5c33e5815cf499fe/src/templates/common/apis/OAI_record.xml#L34

In JATS, the copyright statement is hardcoded: https://github.com/BirkbeckCTP/janeway/blob/959d7ddf5eed21aa02fc80bc5c33e5815cf499fe/src/templates/common/encoding/article_jats_1_2.xml#L65

Because licenses and rights statements are different things, we should make sure each one is represented in each serialization as well as it can be.

In DC, what if we pull Article.rights_statement into dc:rights and add a line for dc:license to pull in the license URI?

In JATS, what if we include the tag license alongside copyright-statement and pull in the same two fields? NLM has this example:

 <permissions>
  <copyright-statement>Copyright: &copy; 2004 Eichenberger
   et al.</copyright-statement>
  <copyright-year>2004</copyright-year>
  <license license-type="open-access"
    xlink:href="http://creativecommons.org/licenses/by/2.0/">
   <license-p>This is an open-access article distributed under the 
    terms of the Creative Commons Attribution License, which permits 
    unrestricted use, distribution, and reproduction in any medium, 
    provided the original work is properly cited.</license-p>
  </license>
 </permissions>

Janeway version 1.4.3

[ajrbyers]

This looks like a good plan @joemull