lte_lpp: telcom-parser: genreate ASN.1 & rust bindings

[philgebhardt]

This is a prerequisite PR for #1072, providing the LPP rust bindings
needed for the analyzer.

All of the code within this commit was generated from official 3GPP
TS 37.355 spec material, using tooling from the hampi project.
The following are the steps taken to generate both the ASN.1 and rust
bindings.

Generating ASN.1

This ASN.1 is the output of hampi parsing over the 3GPP TS 37.355 spec
(version 19.3.0, 37355-j30.docx) found on the 3GPP Portal.

This was generated using my fork of hampi's parser example. The
purpose of this fork is to separate LPP-PDU-Definitions.asn from
LPP-Broadcast-Definitions.asn. Only the former are needed for the LPP
message parsing that poweres the LPP analyzer. The out-of-the-box example
in the official hampi repo combines these asn definitions into a single
file.

python3 /git/hampi/parse-spec/extract-definitions/examples/specs/parse_spec.py 37355-j30.docx -d telcom-parser/specs

Generating Rust Bindings

Generating these bindings from the above ASN.1 output requires a version
of hampi with the fix for ystero-dev/hampi#143.
At the time of this writing that fix is merged to hampi's master branch,
but not yet released to the cargo install distribution. It can be
run directly from hampi source with the following.

cargo run --bin rs-asn1c -- --codec uper --module /git/rayhunter/1072/lte-lpp-definitions/telcom-parser/src/lte_lpp.rs -- /git/rayhunter/1072/lte-lpp-definitions/telcom-parser/specs/LPP-PDU-Definitions.asn

See: #1072

Pull Request Checklist

• The Rayhunter team has recently expressed interest in reviewing a PR for this.
  • If not, this PR may be closed due our limited resources and need to prioritize how we spend them.
• Added or updated any documentation as needed to support the changes in this PR.
• Code has been linted and run through cargo fmt.
• If any new functionality has been added, unit tests were also added.
• CONTRIBUTING.md has been read.
• Your pull request is fewer than ~400 lines of code.

You must check one of:

• No generative AI (including LLMs) tools were used to create this PR.
• Generative AI was used to create this PR. I certify that I have read and understand the code, and that all comments and descriptions were authored by myself and are not the product of generative AI.