[MRELEASE-1150] mvn release:perform should also invoke git lfs checkout after cloning the repo

**[zosrothko](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=zosrothko)** opened **[MRELEASE-1150](https://issues.apache.org/jira/browse/MRELEASE-1150?redirect=false)** and commented

Hello

While the maven-release-plugin:perform is cloning a git repository in the 'target/checkout' subdirectory, it does not run the command 'git lfs checkout' to upate all lfs files with their real content which produces build failures like below

`[ERROR] Failed to execute goal org.codehaus.izpack:izpack-maven-plugin:5.2.1:izpack (default) on project installer-izpack: Failure during compilation process: No compression or archiving format detected for file ...\izpack\target\.\wildfly\wildfly-22.0.0.Final.zip marked to be unpacked while processing ./wildfly/wildfly-22.0.0.Final.zip -> [Help 1]`

Without the 'git lfs checkout' command, the content of the above zip file is

`version https://git-lfs.github.com/spec/v1`
`oid sha256:9ac7490e2624a1bd73af89c6db25900031bdb6c673f2acd375f7e8c102a0d0d7`
`size 203150891`

`which is not a zip file.`

Please add a option to run 'git lfs checkout' as needed for maven-release-plugin:perform

---

**Affects:** 3.1.0

Start with the maven-release-plugin:perform flow that clones into target/checkout and review how external Git commands are handled. Add an option that conditionally runs git lfs checkout after cloning, then verify that LFS-tracked files contain their real contents and that the release perform flow still works when the option is unused.

Written by the indexing model from the issue text.