[BUG] create_future_initial_message notification doesn't seem to get sent on --define-cloud anymore.

[sadsfae]

We should be sending a notification when a new environment is defined via create_future_initial_message https://github.com/redhat-performance/quads/blob/2.1/src/quads/tools/notify.py#L132

This should deliver the following templated email notification at that time: https://github.com/redhat-performance/quads/blob/2.1/src/quads/templates/future_initial_message

Instead, post 2.1.0 (development) we see it not arriving at all, it should have a subject line of New QUADS Assignment Defined for the Future:

In postfix logs this should be for example the first message sent today (2024-09-27) but I see what looks like an attempt to parse and send the message but not complete it, so this may be where the end of the failure trail stops:

Sep 27 11:20:02 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: connect from localhost[127.0.0.1]
Sep 27 11:20:02 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: 85EB54099768: client=localhost[127.0.0.1]
Sep 27 11:20:02 quads2-stage.rdu2.example.com postfix/cleanup[1476398]: 85EB54099768: message-id=<20240927112002.85EB54099768@quads2-stage.
rdu2.example.com>
Sep 27 11:20:02 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=6 data=1 quit
=1 commands=10
Sep 27 11:20:02 quads2-stage.rdu2.example.com postfix/qmgr[72167]: 85EB54099768: from=<[email protected]>, size=1399, nrcpt=5 (queue active)
Sep 27 11:20:03 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: connect from localhost[127.0.0.1]
Sep 27 11:20:03 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: B6C014099769: client=localhost[127.0.0.1]
Sep 27 11:20:03 quads2-stage.rdu2.example.com postfix/cleanup[1476398]: B6C014099769: message-id=<20240927112003.B6C014099769@quads2-stage.
rdu2.example.com>
Sep 27 11:20:03 quads2-stage.rdu2.example.com postfix/smtpd[1476395]: disconnect from localhost[127.0.0.1] ehlo=1 mail=1 rcpt=6 data=1 quit
=1 commands=10

[sadsfae]

I'm going to close this, I am not sure it's a bug because subsequent tests passed with a different cloud. If I see this behaviour again we'll re-open. The only thing that comes to mind here is somehow the environment we used before had already gotten its flagged reset for receiving that notification in some form before.