[FEATURE] Prepare for Release of Version 0.4.0

[TheCedarPrince]

We need to release the new version of OMOPCDMCohortCreator after some heroic work by @Jay-sanjay in #61 and some other API changes. Here's what needs to be done:

• [x] Update CHANGELOG.md
• [x] Update Citation.cff with:
  • [x] New version number
  • [x] New author information
  • [x] Release Date
• [x] Update Project.toml with
  • [x] New author information
  • [x] New Version number

This needs to go into a new PR based off of the dev branch and prepared for merging into the main. I'll review that PR and then once it's merged, we can call the JuliaRegistrator bot! :smiley:

[TheCedarPrince]

@Jay-sanjay now that we got that PR merged in, here is how to tag a release:

1. Go to issue #1
2. Within a comment, say @JuliaRegistrator register()
3. Watch the issue thread to make sure nothing gets messed up in the release

Then we are good to go! Let me know if you have any problems!

P.S. Please leave #1 open -- it's just a practice I use to have a single issue open on a Julia repository for whenever I want to release a package.

[JuliaRegistrator]

Registration pull request created: JuliaRegistries/General/96251

Tip: Release Notes

Did you know you can add release notes too? Just add markdown formatted text underneath the comment after the text "Release notes:" and it will be added to the registry PR, and if TagBot is installed it will also be added to the release that TagBot creates. i.e.

@JuliaRegistrator register

Release notes:

## Breaking changes

- blah

To add them here just re-invoke and the PR will be updated.

Tagging

After the above pull request is merged, it is recommended that a tag is created on this repository for the registered package version.

This will be done automatically if the Julia TagBot GitHub Action is installed, or can be done manually through the github interface, or via:

git tag -a v0.4.0 -m "<description of version>" ac5bcf02a67ff0afe7868c6d77b61674daa2795e
git push origin v0.4.0