Specify available moves explicitly

[soheilshahrouz]

Currently, we pass the number of available moves to the KArmedBanditAgent's constructor to specify which moves are available. This interface assumes that move types have a specific order. This PR changes the interface so that available moves can be specified explicitly.

The main motivation for this PR is to add NoC-specific move types that are disabled for conventional architectures.

Types of changes

• Bug fix (change which fixes an issue)
• New feature (change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My change requires a change to the documentation
• I have updated the documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed

[vaughnbetz]

One suggested clean up (use a vector of names / properties) for the move types.

[soheilshahrouz]

@vaughnbetz

I applied your comments. Here is the link to QoR for Titan that shows the new interface for specifying availale move types does not degraged the runtime.