chores(deps): Bump armeria.version from 1.17.2 to 1.24.3

[darkmastermindz]

Resolves CVE-2023-38493 (Issue #3556)
Bump netty.version to align to latest
Bump jackson.version to align to latest
Bump micrometer.version to align to latest

Ref: https://netty.io/news/2023/07/27/4-1-96-Final.html https://mvnrepository.com/artifact/com.linecorp.armeria/armeria/1.24.3

[darkmastermindz]

Looks like the time elapsed was 3.054 seconds which is 0.054s more than the test expectations. Not sure if this still in acceptable range.

zipkin/zipkin-server/src/test/java/zipkin2/server/internal/elasticsearch/ITElasticsearchClientInitialization.java

Lines 46 to 61 in d0bdc80

	/** blocking a little is ok, but blocking forever is not. */
	@Test(timeout = 3000L) public void doesntHangWhenAllDown() throws IOException {
	TestPropertyValues.of(
	"spring.config.name=zipkin-server",
	"zipkin.storage.type:elasticsearch",
	"zipkin.storage.elasticsearch.timeout:1000",
	"zipkin.storage.elasticsearch.hosts:127.0.0.1:1234,127.0.0.1:5678")
	.applyTo(context);
	Access.registerElasticsearch(context);
	context.refresh();
	try (ElasticsearchStorage storage = context.getBean(ElasticsearchStorage.class)) {
	CheckResult result = storage.check();
	assertThat(result.ok()).isFalse();
	}
	}

[darkmastermindz]

@llinder could you please review, thanks!

[darkmastermindz]

Trying to see if bumping protobuf CVE issue will help with benchmarks

[debraj-manna]

Can someone let me know when is this expected to be merged?

[codefromthecrypt]

I will be helping with all this stuff this week. Sorry about the neglect experience. let's work together to fix it.

@darkmastermindz are you running a zipkin site or is this a hobby effort for you?

[codefromthecrypt]

@debraj-manna the project team basically haven't been working out well as this has proven out. I'm going to clean as much of the PR queue as I can, and later raise an issue to help build an on-ramp for new maintainers, who have stake in PRs landing, especially ones like this. Apologies on behalf of this accidental situation... basically I think all the historical maintainers aren't running sites anymore and this is a problem to fix.

[codefromthecrypt]

ps if you'd like to rebase with latest armeria (make sure affected versions also match armeria), go for it. Otherwise, I'll help with your branch tomorrow. We'll get this sorted by tomorrow either way.

[codefromthecrypt]

working on this now

[codefromthecrypt]

I don't have write access to your branch, so I pulled the change into #3614. I dropped the protobuf update as it only affected benchmarks (not production code). I'll update proto in a different PR to latest along with any other deps only used in benchmarks. Thanks again for the help!

[darkmastermindz]

I will be helping with all this stuff this week. Sorry about the neglect experience. let's work together to fix it.

@darkmastermindz are you running a zipkin site or is this a hobby effort for you?

@codefromthecrypt Thanks for the help on this! Apologies for the unresponsiveness as I've been on holiday. This is mostly has become a hobby effort. Previously, I was running zipkin site for an Enterprise organization. Generally, I'm open in helping contribute and help maintain open source telemetry projects.