Creating draft release with inputFilePath specified does not use content

[AdmiringWorm]

Description

When you create a draft release using git release manager and have specified the file to use in release notes using the --inputFilePath argument, it is not being used when drafting the release notes.
Instead it collects the issues needed in the same way as if you never specified the input file path.

Expected Behavior

I would expect GRM to make use of the file that was specified as an inputFilePath instead of doing its own collection of the issues to add.

Actual Behavior

Already mentioned, but GRM create always collects the issues it want, instead of respecting the input file path argument.

Possible Fix

Unknown

Steps to Reproduce

1. Create a text file with the release notes to use
2. Run dotnet gitreleasemanager create --token "<GITHUB_TOKEN>" -o "<REPO_USER>" -r "<REPO_NAME>" -m "0.1.0" -i "<PATH_TO_RELEASE_NOTES>" -c "<BRANCH>"
3. Look at release notes and notice nothing from the specified file was used.

Context

Unable to create the release notes automatically for repositories not following the same convertion as GRM.

Your Environment

• Version Used: 13.0, 12.1 and 12.0 (could not test earlier versions)
• Edition Used (.NET Core, .NET Framework): .NET Core
• Operating System and version (Windows 10, Ubuntu 18.04): Windows 11
• Link to your project: https://github.com/AdmiringWorm/VideoConverter
• Link to your CI build (if appropriate): N/A

[AdmiringWorm]

When looking at this, it looks more like we need some validation.

Using a milestone combined with an input file path is incompatible with each other, so we should probably throw an exception in the beginning with this invalid combination instead.

As such, I'll change this to a breaking change instead.