Fix nil flag client, and warn about use in future

[evankanderson]

Summary

When merging #4784, I missed that I needed to update services.go to pass the flag client. This led to a nil interface in Bool() and a panic.

Change Type

Mark the type of change your PR introduces:

• Bug fix (resolves an issue without affecting existing features)
• Feature (adds new functionality without breaking changes)
• Breaking change (may impact existing functionalities or require documentation updates)
• Documentation (updates or additions to documentation)
• Refactoring or test improvements (no bug fixes or new functionality)

Testing

This shows up real fast as a failure to publish messages when running the server. The panic is caught, but no message is published.

Review Checklist:

• Reviewed my own code for quality and clarity.
• Added comments to complex or tricky code sections.
• Updated any affected documentation.
• Included tests that validate the fix or feature.
• Checked that related changes are merged.

[coveralls]

Pull Request Test Coverage Report for Build 11690393097

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 1 of 5 (20.0%) changed or added relevant lines in 2 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage decreased (-0.006%) to 54.763%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/service/service.go	0	1	0.0%
internal/flags/flags.go	1	4	25.0%

Totals
Change from base Build 11689795417:	-0.006%
Covered Lines:	15534
Relevant Lines:	28366

---

💛 - Coveralls