refs #390: there is no license link when editing an existing module sinc...

...e the user has already accepted the license.

On the summary we have a message stating that the user needs to accept the CNX license before publication. We supply a link to the license acceptance page.

We recently added a new workflow where the user can edit or overwrite an existing CNX module. When users create module in CNX, they are force to accept the license during module creation. Thus, when targeting an existing in the OERPUB workflows the license acceptance is no longer required.

When we process what SWORD publishing returns to us, we look for the "accept license" link. The problem was that the code unconditionally looked for the link. The fix was to have the code conditionally look for the link.