Create new usb constants

[epenet]

Breaking change

Create usb constants.

As requested by @bdraco in #60042

Proposed change

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New integration (thank you!)
• New feature (which adds functionality to an existing integration)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast homeassistant tests)
• Tests have been added to verify that the new code works.

If user exposed functionality or configuration variables are added/changed:

• Documentation added/updated for www.home-assistant.io

If the code communicates with devices, web services, or third-party tools:

• The manifest file has all fields filled out correctly.
  Updated and included derived files by running: python3 -m script.hassfest.
• New or updated dependencies have been added to requirements_all.txt.
  Updated by running python3 -m script.gen_requirements_all.
• For the updated dependencies - a link to the changelog, or at minimum a diff between library versions is added to the PR description.
• Untested files have been added to .coveragerc.

The integration reached or maintains the following Integration Quality Scale:

• No score or internal
• 🥈 Silver
• 🥇 Gold
• 🏆 Platinum

To help with the load of incoming pull requests:

• I have reviewed two other open pull requests in this repository.

[probot-home-assistant]

Hey there @bdraco, mind taking a look at this pull request as it has been labeled with an integration (usb) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[probot-home-assistant]

Hey there @tkdrob, mind taking a look at this pull request as it has been labeled with an integration (modem_callerid) you are listed as a code owner for? Thanks!
_{^{(message by CodeOwnersMention)}}

[epenet]

I have taken out the "ATTR_DEVICE" constant as @frenck would say it is dead code (until another component needs it).
I will re-add it in the modem_callerid PR #60042.

Should I use the constants in the new_usb variables? new_usb is a mock from async_get_usb which comes from loader.py so I decided to keep them separate, but I can update the tests if you request it.

     new_usb = [
        {"domain": "test1", "vid": "3039", "pid": "3039", "description": "*2652*"}
    ]

vs

     new_usb = [
        {"domain": "test1", usb.ATTR_VID: "3039", usb.ATTR_PID: "3039", usb.ATTR_DESCRIPTION: "*2652*"}
    ]

[bdraco]

Actually let's leave ATTR_DEVICE in here so we don't have changes to two integrations in the same PR if we can avoid it