manage WICS projects

Add ITS::WICS::Project.pm with tests, test data, and a share directory
containing the current version of the WICS viewer code. Project.pm
can update a WICS "project" folder to contain the latest WICS viewing
code in a ".WICS" folder. It uses a "VERSION" file to determine if
it should not overwrite the directory files.

I have not managed versions manually before, so I hope that I have used
a safe strategy. Basically leave alone anything that's newer than the
current version. Overwrite files of current version or older. Ignore
extraneous files instead of deleting them. Hopefully the WICS viewer
code will always use the same directory structure and filenames.
code_links method for linking HTML with viewer code

Add a "code_links" method which returns a list of ITS::DOM elements
that are needed to link HTML files in the project with the viewer
code contained in the .WICS folder.
link_code function to add links to HTML document

Implement a link_code function which, given an HTML document, adds the
appropriate links to make the document ITS viewable. Also test.

Also fix the links that are created- <script> elements should have
"src", not "href".
allow use of projects in WICS and WICS-GUI

Allow using projects through WICS and WICS-GUI. Add a new option
to WICS, -p or --project, to specify the project directory. In
WICS-GUI, provide a checkbox that triggers a directory selection
when the "convert" button is clicked.

Still needs documentation.
document use of projects in WICS and WICS-GUI

Add documentation to WICS, WICS-GUI, and the User Guide on how
to use projects. Document the current limitations of the dynamic
viewer, and replace the old converter screenshot to show the new
checkbox.
use File::ShareDir::PAR

Use File::ShareDir::PAR so that PAR will be able to find the shared
files after packaging the application into an exe.