`pygettext` generates output even when there should be none

Bug report

Bug description:

This occurs in two cases:

• Output is still generated when there is no input. Whereas xgettext:

  $ xgettext
  xgettext: no input file given
  Try 'xgettext --help' for more information.
  

  And the second case follows on from this (but can also occur with input files)
• In xgettext, no output is generated if there are no messages. In pygettext output is still generate even if no messages are found, the header is still sent.
  We should fix it to work like xgettext and not produce "empty" output.

cc @tomasr8

CPython versions tested on:

CPython main branch

Operating systems tested on:

No response

Linked PRs

• gh-156322

Start at the pygettext command-line entry point and compare its no-input and no-message behavior with xgettext. Confirm that both cases produce no output, then check the existing pygettext tests or add coverage for these two scenarios; the linked PR gh-156322 indicates work may already be underway.