Feature/handle yearly rrule

[shiveenp]

Description

Adds support for yearly rule with an implementation that matches lunartick

[ordermentum]

Please make sure to add screenshots or gifs of the change to give a clear
picture of the change. If a design PR was made please make sure to link to it along with the
JIRA ticket. A Design PR will avoid unnecessary rework that might come up in a PR.

Good Pull Requests adhere to a single responsibility.

• Break big changes into smaller Pull Requests
• Big changes increase risk - smaller PRs are easier to review
• Refactoring changes should be in seperate PRs to avoid noise
• A story/ticket can have more than 1 PR

Some guidelines on giving and receiving feedback in Code Reviews

• https://blog.rangle.io/the-art-of-humanizing-pull-requests-prs/
• https://blog.scottnonnenberg.com/top-ten-pull-request-review-mistakes/
• https://dev.to/codemouse92/10-principles-of-a-good-code-review-2egA
• https://dev.to/samjarman/giving-and-receiving-great-code-reviews