Designate-agent package should not be created for 18.0.0 (Caracal/2024.1)

[Bartosz Woronicz]

The designate-agent binary was removed in Caracal release:

Please see the release notes here:
https://docs.openstack.org/releasenotes/designate/2024.1.html
>Designate-agent removal is complete in this version of designate.

I also see that the package still exist while it should be removed
ubuntu@juju-8a251a-6-lxd-0:~$ apt-cache policy show designate-agent
designate-agent:
  Installed: 1:14.0.4-0ubuntu1
  Candidate: 1:18.0.0-0ubuntu1~cloud0
  Version table:
     1:18.0.0-0ubuntu1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/caracal/main amd64 Packages

This package contains auto-generated (with openstack-pkg-tools) service:
ubuntu@juju-8a251a-6-lxd-0:~$ dpkg -L designate-agent
/.
/etc
/etc/init.d
/etc/init.d/designate-agent
/lib
/lib/systemd
/lib/systemd/system
/lib/systemd/system/designate-agent.service
/usr
/usr/share
/usr/share/doc
/usr/share/doc/designate-agent
/usr/share/doc/designate-agent/copyright
/usr/share/doc/designate-agent/changelog.Debian.gz
ubuntu@juju-8a251a-6-lxd-0:~$ apt-cache policy show python3-designate
python3-designate:
  Installed: 1:18.0.0-0ubuntu1~cloud0
  Candidate: 1:18.0.0-0ubuntu1~cloud0
  Version table:
 *** 1:18.0.0-0ubuntu1~cloud0 500
        500 http://ubuntu-cloud.archive.canonical.com/ubuntu jammy-updates/caracal/main amd64 Packages
        100 /var/lib/dpkg/status

Yet the actual binary used to be packaged as /usr/bin/designate-agent in python3-designate, while it is not now
ubuntu@juju-8a251a-6-lxd-0:~$ dpkg -L python3-designate|grep bin
/usr/bin
/usr/bin/designate-api
/usr/bin/designate-api-wsgi
/usr/bin/designate-central
/usr/bin/designate-manage
/usr/bin/designate-mdns
/usr/bin/designate-producer
/usr/bin/designate-rootwrap
/usr/bin/designate-sink
/usr/bin/designate-status
/usr/bin/designate-worker
/usr/lib/python3/dist-packages/designate/backend/impl_bind9.py
/usr/lib/python3/dist-packages/designate/tests/unit/backend/test_bind9.py

The proposed solution would be either:
1. keep the boilerplatte package designate-charm but remove the service designate-agent
2. remove the package entirely and do not create version 18.0.0-x of designate-agent

[Bartosz Woronicz (mastier1)]

This is related bug report for the charm:
https://bugs.launchpad.net/charm-designate/+bug/2065596