Do not merge: Adding transform configuration for playtest purposes

[fluong6]

Description

Issue Number(s)

Contribution checklist

• Tests have been added for the project and/or any internal package
• Release notes have been added to the project changelog file
• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• JIRA ticket ID is in the PR title or at least one commit message
• Include the ticket ID number within the body message of the PR to create a hyperlink

[NoelStephensUnity]

Looks great!
You can select with a mouse or by hitting the corresponding numeric key.
I updated the manifest to point to develop until the v1.5.2 branch is created.
Other than that, I think we are good to go as far as using the ClientDriven for hosted tests.
We will circle back to do the content selection stuff.
👍 💯

[NoelStephensUnity]

@fluong6
You might want to remove the Windows Build folder.

[fluong6]

@NoelStephensUnity Since we are using ClientDriven_TestingTool branch as our main ClientDriven Test tool branch for our playtest, I was planning to use this branch (feature/adding-transform-configuration) as a sandbox.

Last night before, I was making change locally in a window machine at the office and planned to continue to work on those changes at home today. That's why I committed everything. 😛

Reverting the changes soon.

[unity-cla-assistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ NoelStephensUnity
❌ fluong6
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[RikuTheFuffs]

@fluong6 and @NoelStephensUnity doing some cleanup here, is this PR still needed or can we close it?