Add support for building Debian packages

[esteve]

This PR add the infrastructure for building a Debian package., it's based on the output from stdeb. I've added Cargo.lock to Git so we can make sure the resulting binary builds the same as the wheel on PyPI.

[esteve]

@cottsay this should help with uploading cargo-build-ament to PackageCloud. Please let me know if there's anything that should be addressed. Thanks.

[j-rivero]

Hello @esteve ! I volunteer from the Infra PMC to follow this .deb production. @cottsay mentioned that this is mostly a transitional package until the functionality is merged into colcon-cargo (if I remember correctly).

One idea before before moving the stddeb based work forward: instead of hosting a custom copy of the debian/ metadata to avoid more metadata containers we could use the cargo deb crate to generate a .deb package hosting a bit more information in the cargo.toml metadata, see a quick prototype.

If we follow with the stddeb approach, I added some fixes on top of the produced debian/ metadata in j-rivero/cargo-ament-build@main...jrivero/add-stdeb. With the approach of using stddeb + manual curation we can get a higher quality .deb but I'm no sure if for this case worth the effort.

Comparing both debians:

stddeb in the left vs cargo deb in the right:

The control file:

There are some differences in the libc6 required but we should be able to deal with them.

My take here would be, if we are mainly interested into distributing the binary cargo-ament-build we can avoid adding more machinery to the rust + python mix and use the cargo deb version.