feat: support monorepos

[crqrdotcom]

Partially fixes #7

• Add global option --project (aliased -p) to specify the project we want to work with in a monorepo
• Adds support to work seamlessly with previous tags that were prefixed with v
• Support managing multiple tags with multiple versions in a monorepo

NEXT:

• Only consider version updates from commits done inside the directory specified by --project
• Make the default value for --project the user's working directory

Will create separate issues for these as they're non-blocking for the feature in review

[jsmvaldivia]

I feel like whenever you are calling a piece of code that returns a value and an err, you could wrap it up in an unexported func. You might end with several seemingly useless functions but when maintaining, one typically reads the exported ones first and try to figure out at a higher level what do they do exactly. IMO having all the error handling within the exported function code reduces that readability

[crqrdotcom]

I feel like whenever you are calling a piece of code that returns a value and an err, you could wrap it up in an unexported func. You might end with several seemingly useless functions but when maintaining, one typically reads the exported ones first and try to figure out at a higher level what do they do exactly. IMO having all the error handling within the exported function code reduces that readability

I agree with your comment and after changing accordingly can see the benefits already. Thanks!