Unified platform handling and fetching of operator score files

[parthosa]

Fixes #616.

This PR fixes the below issues related to platform argument:

1. Correct platform handling
   • Original scope to handle case when the platform provided is incorrect in Qualification tools.
2. Unified platform handling
   • Based on [BUG] Qualification tool: Invalid --platform doesn't error #616 (comment), it came out that the platform argument handling was different in Profiling and Qualification tools.
3. Improve fetching of operator score files
   • Revise fetching of operator score files based on platform name. It is currently hardcoded for specific platforms and GPU types.

Major Changes:

1. Platform.scala:
   • Moved Platform.scala outside the profiler package for shared use.
   • Added PlatformNames to store platform strings as constants.
   • Added PlatformFactory to create Platform instances based on platform string values.
     • Handles cases where the platform is incorrect (original issue). Addresses #1
     • Both Profiler and Qualification tool use createInstance() to get platform instance. Addresses #2
2. PluginTypeChecker.scala:
   • Use method getOperatorScoreFile() defined in Platform.scala for dynamic filename generation of operator score files. Addresses #3

Follow Up:

• Currently there are many instances (unit tests, default value) where platform is still passed as a string value. I plan to submit a follow up PR to replace all of them with the constants defined in PlatformNames class.

[kuhushukla]

LGTM overall. Would it be right to say that the operator score changes here allow for filenames that tell us which platform they are for and not necessarily the score aspect of it? Thank you.