fix debian package generation process and add to CI

[bennibbelink]

Closes #592. Adds steps to publish_release.yml to build a Debian package and upload it to the release.

[github-actions]

Build Status Report - 73c2dc8 - 2024-04-05 01:40:29 +0000

Build FROM cyclus_20.04_apt/cyclus:latest

• Cycamore: Success ✅
• Cymetric: Success ✅

Build FROM cyclus_20.04_apt/cyclus:stable

• Cycamore: Failure ❌
• Cymetric: Skipped due to upstream failure ⚠️

Build FROM cyclus_20.04_conda/cyclus:latest

• Cycamore: Success ✅
• Cymetric: Success ✅

Build FROM cyclus_20.04_conda/cyclus:stable

• Cycamore: Failure ❌
• Cymetric: Skipped due to upstream failure ⚠️

Build FROM cyclus_22.04_apt/cyclus:latest

• Cycamore: Success ✅
• Cymetric: Success ✅

Build FROM cyclus_22.04_apt/cyclus:stable

• Cycamore: Failure ❌
• Cymetric: Skipped due to upstream failure ⚠️

Build FROM cyclus_22.04_conda/cyclus:latest

• Cycamore: Success ✅
• Cymetric: Success ✅

Build FROM cyclus_22.04_conda/cyclus:stable

• Cycamore: Failure ❌
• Cymetric: Skipped due to upstream failure ⚠️

[bennibbelink]

Tested on my fork - https://github.com/bennibbelink/cycamore/releases/tag/1.6.4

I'm able to install cycamore on a fresh ubuntu:22.04 image using the cyclus .deb and cycamore .deb, all cycamore_unit_tests pass.

[bennibbelink]

Unfortunately CI won't pass on this PR until a cyclus:stable image exists.

[gonuke]

Do you think we should wait to merge, or go ahead now, and repair if there are issues later

[bennibbelink]

Best practice would probably suggest we wait. However, potential issues would likely be noticed in the Cyclus release first since they follow the same general procedure - so we would have the opportunity to apply fixes before we issue a cycamore release. I think I lean towards merging and getting the two repos in the same state now (in terms of Deb generation) instead of having them out of sync and trying to catch up cycamore and patch issues all in one go.

[gonuke]

Thanks @bennibbelink - let's see how this works on our release.