Fix AT-URI parsing and knot routing in PR merge
Three bugs fixed:
1. parse_target_repo_info and parse_record_id expected 4 parts in a split
AT-URI but valid AT-URIs only have 3 parts after stripping the at://
prefix (in both pr.rs and issue.rs).
2. PR merge sent requests to the default tngl.sh gateway instead of the
actual knot hosting the repo, causing service auth token verification
to fail.
3. merge_pull used post_json but the merge endpoint returns an empty body
on success, causing a JSON parse error.