Idea: move Emscripten include path injection and depending on emscripten sdk into build.zig

[floooh]

...we're iterating over the C library dependencies here anyway:

sokol-zig/build.zig

Lines 351 to 367 in d9f3ef9

	emcc.addArtifactArg(options.lib_main);
	var it = options.lib_main.root_module.iterateDependencies(options.lib_main, false);
	while (it.next()) |item| {
	for (item.module.link_objects.items) |link_object| {
	switch (link_object) {
	.other_step => |compile_step| {
	switch (compile_step.kind) {
	.lib => {
	emcc.addArtifactArg(compile_step);
	},
	else => {},
	}
	},
	else => {},
	}
	}
	}

...maybe the Emscripten include path could be injected there, as well as depending on the Emscripten SDK setup step? That way the toplevel project wouldn't need to take care of that, and it's needed for every C library anyway.