no need to kill nextjs on package change

[adhami3310]

also adds helpful messages

[codspeed-hq]

CodSpeed Performance Report

Merging #5389 will not alter performance

_{Comparing no-need-to-kill-nextjs-on-package-change (0db6f89) with main (8c24e8f)}

Summary

✅ 8 untouched benchmarks

[Lendemor]

Suggested change

	dependencies_change = get_changes(
	old_package_json_content.get("dependencies", {}),
	new_package_json_content.get("dependencies", {}),
	)
	dev_dependencies_change = get_changes(
	old_package_json_content.get("devDependencies", {}),
	new_package_json_content.get("devDependencies", {}),
	)
	return dependencies_change, dev_dependencies_change
	return tuple(
	get_changes(
	old_package_json_content.get(deps_key, {}),
	new_package_json_content.get(deps_key, {}),
	)
	for deps_key in PackageJson.__annotations__
	)

[adhami3310]

this makes the typing looser, so i would prefer to keep explicit for now

[Lendemor]

Make sense for the explicit.

Are the intermediary variable just there for easier reading ? because we could do explicit in the return expression right?

[adhami3310]

just there for easier reading

yea it's also to declutter a long return line