Describe the bug
Weaver panics.

To Reproduce
Steps to reproduce the behavior:

1. Check out commit a3adbb3b59cfdfa2e2c75b7bdbc3a1cd22510836 from https://github.com/open-telemetry/semantic-conventions
2. Run make table-check

Expected behavior
Weaver to successfully complete the check and compliment me for the awesomeness of the change.

Additional context
I am wildly speculating here, but Weaver may be emotionally attached to the peer.service attribute of semconvs.