Bump the HDRP Template IET Framework Package Version

[johnpars]

Purpose of this PR

This is a tiny PR that bumps the template project IET package version from 2.0 -> 2.1 release to fix a memory leak caused for the tutorial, and was reported here: https://fogbugz.unity3d.com/f/cases/1374640/

It looks like the editor also automatically bumped the version of Cinemachine and the input system to the latest stable release as well. I decided it was safe to leave this be as I did not observe any issues in the template from that update, but QA may want to ensure this.

---

Testing status

I manually verified that the memory leak caused by the tutorial was no longer flagged in the console.

To QA, the issue was coming from the tutorial framework, so the area of interest to validate would be in the tutorial.

---

Comments to reviewers

More relevant details on the leak in this thread: https://unity.slack.com/archives/C9H0ZN55H/p1633459566022800

[github-actions]

Hi! This comment will help you figure out which jobs to run before merging your PR. The suggestions are dynamic based on what files you have changed.
Link to Yamato: https://unity-ci.cds.internal.unity3d.com/project/902/
Search for your PR branch using the search bar at the top, then add the following segment(s) to the end of the URL (you may need multiple tabs depending on how many packages you change)

HDRP
/jobDefinition/.yamato%2Fall-hdrp.yml%23PR_HDRP_trunk
With changes to HDRP packages, you should also run
/jobDefinition/.yamato%2Fall-lightmapping.yml%23PR_Lightmapping_trunk

Depending on the scope of your PR, you may need to run more jobs than what has been suggested. Please speak to your lead or a Graphics SDET (#devs-graphics-automation) if you are unsure.

[johnpars]

Note: I launched Yamato to test the template projects and not the HDRP PR since this doesn't effect the HDRP runtime in any way.

[kecho]

@johnpars
Looks like yamato caught some bullshit?
https://unity-ci.cds.internal.unity3d.com/job/9571116

You might have to investigate :(

[19:17:39.167 Information] [UPM-CI-UTILS] DEBUG - Running command: npm view upm-ci-utils@stable --json version name --registry https://artifactory.prd.it.unity3d.com/artifactory/api/npm/upm-npm --loglevel silent

[19:17:41.603 Information] [UPM-CI-UTILS] DEBUG - Sending Analytics events. Found 1 event to send

[19:17:41.610 Information] [UPM-CI-UTILS] DEBUG - Package com.unity.cinemachine@2.8.0 in package.json is different to com.unity.cinemachine@2.8.1 in manifest.json. Please validate that package.json dependencies match the template's manifest.json

[19:17:41.616 Information] [UPM-CI-UTILS] DEBUG - Package com.unity.inputsystem@1.1.0-pre.5 in package.json is different to com.unity.inputsystem@1.1.1 in manifest.json. Please validate that package.json dependencies match the template's manifest.json
[UPM-CI-UTILS] DEBUG - Package com.unity.learn.iet-framework@2.0.0 in package.json is different to com.unity.learn.iet-framework@2.1.0 in manifest.json. Please validate that package.json dependencies match the template's manifest.json

[19:17:41.654 Information] [UPM-CI-UTILS] INFO - upm-ci exit code 1

[19:17:41.690 Information] Process exited
[19:17:41.697 Information] Command failed.
[19:17:41.719 Information] Unexpected ExitCode 1 (expected 0)
[19:17:41.867 Information] Commands finished with result: Failed
[19:17:41.874 Information] Starting After Block

[kecho]

Investigate yamato fail, upm-i exit code 1

[johnpars]

Oh weird, guess it didn't like that I changed the manifest. Will dig in

[johnpars]

Should be fixed, forgot to update the package dependency. Re-running..

Edit: We are 🟢

[remi-chapelain]

Repro project seems enough to verify that this is indeed fixed.