Parse event qualifiers for the Rocm and Cuda components to make sure no excess characters are appended

[Treece-Burgess]

Pull Request Description

For both the Cuda component and the Rocm component, when adding events there is a an edge case where a user could successfully add events that had excess characters after the appended qualifier. Example of this is shown below with the Cuda component:

./papi_command_line cuda:::dram__bytes.avg:device=0test

This utility lets you add events from the command line interface to see if they work.

Successfully added: cuda:::dram__bytes.avg:device=0test

cuda:::dram__bytes.avg:device=0test : 	268 

This PR addresses adding conditional checks to test for excess characters and properly return PAPI_ENOEVNT if applicable. The new behavior is outlined below:

./papi_command_line cuda:::dram__bytes.avg:device=0test

This utility lets you add events from the command line interface to see if they work.

Failed adding: cuda:::dram__bytes.avg:device=0test
because: Event does not exist
No events specified!
Try running something like: ./papi_command_line PAPI_TOT_CYC

Author Checklist

• Description
  Why this PR exists. Reference all relevant information, including background, issues, test failures, etc
• Commits
  Commits are self contained and only do one thing
  Commits have a header of the form: module: short description
  Commits have a body (whenever relevant) containing a detailed description of the addressed problem and its solution
• Tests
  The PR needs to pass all the tests