bluetooth: Add version and company identifiers to local version commands

[antoniovazquezblanco]

Checklist:

• If you are new to Scapy: I have checked CONTRIBUTING.md (esp. section submitting-pull-requests)
• I squashed commits belonging together
• I added unit tests or explained why they are not relevant
• I executed the regression tests (using cd test && ./run_tests or tox)
• If the PR is still not finished, please create a Draft Pull Request

Just adds more information to the HCI_Cmd_Complete_Read_Local_Version_Information packet :)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.16%. Comparing base (0648c0d) to head (4456378).

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4716      +/-   ##
==========================================
- Coverage   82.20%   82.16%   -0.04%     
==========================================
  Files         361      343      -18     
  Lines       87195    86924     -271     
==========================================
- Hits        71679    71424     -255     
+ Misses      15516    15500      -16     

Files with missing lines	Coverage Δ
scapy/data.py	90.55% <ø> (-0.28%)	⬇️
scapy/layers/bluetooth.py	90.47% <100.00%> (ø)

... and 276 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[XenoKovah]

It would probably be good to add a comment pointing to https://bitbucket.org/bluetooth-SIG/public/src/main/assigned_numbers/company_identifiers/company_identifiers.yaml where the company identifiers come from, so they can be more easily updated in the future (since they change very frequently).

[gpotter2]

Hi, sorry for the delay. I think that this should be moved to someplace else as it makes bluetooth.py a bit unreadable.

Ideally it would be stored similarly to conf.manufdb (50k entries), which is stored as a base85 compressed & cached blob. Although, considering there are only 3k entries here, I guess that storing the dict in data.py would be acceptable. In all cases, for a dict this big, I would avoid putting it in layers/.

How does that sound?

[antoniovazquezblanco]

Sorry for the delay. Went the easy route and moved the dict to data. :)