[UserStory] Add official release link to website

[jody]

User Story

Essential components

• Title describes the story
• Stakeholder type is identified
• Outcome is described
• Rationale is explicit
• Acceptance criteria are verifiable and from the perspective of the stakeholder

Story

As a user or educator
I want a prebuilt jar file with a corresponding download link corresponding on the website
so that I can use the product jar without having to download sources and build it locally.

Acceptance Criteria

• The project website provides a self-describing link to the current release of the product as a jar file.
• The published API and linked jar file correspond to the same version (release)

Supporting Information

• A release jar file must persist in the repository.
• The release file should not be replaced by the standard build process.
• The API documentation and jar file must agree (represent the same version of the product).
• See: https://docs.github.com/en/repositories/releasing-projects-on-github/about-releases

Dependencies

Depends On

• [UserStory] Rename overall package to better identify the organization #168
  • Must be completed before release candidate is created

Dependents

(Issues dependent on this story)

[Leshy4]

Progress Report:
Our team added to the "build.xml" file and added a "build.properties" file.

**In the build.xml file, we added a variable, the property file "build.properties", added capabilities to build it with the ant build tool through "ant info" in bash, & prints out some pertinent information (Ant version, Website name, release version, & name of release) to the screen after the "ant info" command is run.

**The build.properties file we added variables for "sitename" to link it to the repository, "releaseversion" to keep track of the release version, & "nameofrelease" which has a link to the Redistricting.jar.

[jody]

Added a release to the project (https://github.com/MetroCS/redistricting/releases/tag/v1.0.1)[https://github.com/MetroCS/redistricting/releases/tag/v1.0.1]

Need to check the API documentation and update it if necessary.

[jody]

Updated the API documentation to correspond to v1.0.1