Upgrade nats.c to v3.12.0, add JetStream stream/consumer management

[joshbradshaw11]

Summary

• Upgrades nats.c from v3.10.1 to v3.12.0 (adds per-message TTL, pull consumer priority groups, ObjectStore support; requires OpenSSL 1.1.1+)
• Adds JetStream stream management APIs: addStream, updateStream, deleteStream
• Adds JetStream consumer management APIs: addConsumer, deleteConsumer
• Adds per-message TTL support via JsPublishOptions::msgTTL (new in nats.c v3.11)
• Rewrites integration tests to be fully self-contained — no nats CLI dependency, only nats-server required
• Removes unused JSON config files (stream/consumer setup is now programmatic)

New API surface

// Stream management
JsStreamInfo addStream(const JsStreamConfig& config);
JsStreamInfo updateStream(const JsStreamConfig& config);
bool deleteStream(const QString& name);

// Consumer management
void addConsumer(const QString& stream, const JsConsumerConfig& config);
bool deleteConsumer(const QString& stream, const QString& consumer);

New types: JsStreamConfig, JsStreamState, JsStreamInfo, JsRetentionPolicy, JsStorageType, JsDiscardPolicy

Diffstat (M)

Category	Files	+Lines	-Lines	Size
Production	4	202	11	M
Tests	1	105	68	M
Test assets	3	0	31	S
CMake	1	5	2	XS

Testing

• All JetStream integration tests pass against nats-server v2.12.3
• Tests cover: stream CRUD, sync/async publish, pull subscribe with headers + ack, push subscribe
• Core NATS tests have pre-existing failures (unrelated, depend on nats CLI)

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR upgrades the bundled nats.c dependency to v3.12.0 and expands the QtNats JetStream wrapper with stream/consumer management plus per-message TTL support, while updating JetStream integration tests to be self-contained (no nats CLI).

Changes:

• Upgrade nats.c FetchContent version to v3.12.0.
• Add JetStream stream/consumer management APIs and related public types (JsStreamConfig, JsStreamInfo, enums).
• Update JetStream integration tests to create streams/consumers programmatically and remove JSON test assets.

Reviewed changes

Copilot reviewed 9 out of 9 changed files in this pull request and generated 3 comments.

Show a summary per file

File	Description
CMakeLists.txt	Bumps nats.c version and enables Qt Test for integration tests.
src/qtnats/qtnats.h	Introduces new public JetStream stream-management types/enums and API surface; adds msgTTL publish option.
src/qtnats/qtnats_p.h	Adds RAII deleters for new nats.c info structs and conversion helper for JsStreamConfig; wires msgTTL into jsPubOptions.
src/qtnats/qtnats_p.cpp	Adds conversion from jsStreamInfo to JsStreamInfo.
src/qtnats/jetstream.cpp	Implements addStream/updateStream/deleteStream and addConsumer/deleteConsumer.
test/test_jetstream.cpp	Rewrites JetStream integration tests to avoid nats CLI and manage streams/consumers via the new APIs.
test/stream_config.json	Removed (stream config now created programmatically).
test/pull_consumer_config.json	Removed (consumer config now created programmatically).
test/push_consumer_config.json	Removed (consumer config now created programmatically).

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This test uses C++20 designated initializers (e.g., JsStreamConfig{ .name = ... }), but the project is configured for C++17 (CMAKE_CXX_STANDARD 17). This will fail to compile on standards-conforming C++17 toolchains (notably MSVC). Please either switch these initializations to C++17-compatible aggregate/constructor initialization, or bump the project/test C++ standard to 20 if that’s acceptable.

Suggested change

	js->addStream(JsStreamConfig{
	.name = "TEST_STREAM",
	.subjects = {"test.>"},
	.storage = JsStorageType::Memory,
	});
	JsStreamConfig config;
	config.name = "TEST_STREAM";
	config.subjects = {"test.>"};
	config.storage = JsStorageType::Memory;
	js->addStream(config);

[Copilot]

initTestCase() now calls connectToServer(), jetStream(), and addStream(), all of which can throw QtNats::Exception/JetStreamException on failure. Since initTestCase() doesn’t catch exceptions, a startup failure (server not in PATH, port in use, connection failure, etc.) can terminate the test process instead of producing a clean test failure. Wrap the body of initTestCase() in a try/catch and use QFAIL() (or QVERIFY_EXCEPTION_THROWN-style handling) so the suite fails gracefully.

[Copilot]

cleanupTestCase() calls js->deleteStream() which can throw on network/JetStream errors. Cleanup functions should be resilient: if an exception escapes here it can mask earlier failures and/or crash the test runner. Consider wrapping cleanup operations in try/catch (and best-effort cleanup), and ensure the nats-server process is always terminated even if stream deletion fails.

Suggested change

	if (js) {
	js->deleteStream("TEST_STREAM");
	}
	js = nullptr;
	client.reset();
	natsServer.close();
	natsServer.waitForFinished();
	// Best-effort cleanup: do not let exceptions escape from here.
	try {
	if (js) {
	js->deleteStream("TEST_STREAM");
	}
	} catch (const QException& e) {
	cerr << "Error deleting TEST_STREAM in cleanupTestCase: " << e.what() << endl;
	} catch (const std::exception& e) {
	cerr << "Std exception in cleanupTestCase while deleting TEST_STREAM: " << e.what() << endl;
	} catch (...) {
	cerr << "Unknown exception in cleanupTestCase while deleting TEST_STREAM" << endl;
	}
	js = nullptr;
	client.reset();
	// Ensure the nats-server process is always terminated.
	if (natsServer.state() != QProcess::NotRunning) {
	natsServer.close();
	if (!natsServer.waitForFinished(3000)) {
	natsServer.kill();
	natsServer.waitForFinished();
	}
	}