[bugfix] unwrap boosts when checking in-reply-to status

[NyaaaWhatsUpDoc]

Description

closes #2701

Checklist

• I/we have read the GoToSocial contribution guidelines.
• I/we have discussed the proposed changes already, either in an issue on the repository, or in the Matrix chat.
• I/we have not leveraged AI to create the proposed changes.
• I/we have performed a self-review of added code.
• I/we have written code that is legible and maintainable by others.
• I/we have commented the added code, particularly in hard-to-understand areas.
• I/we have made any necessary changes to documentation.
• I/we have added tests that cover new code.
• I/we have run tests and they pass locally with the changes.
• I/we have run go fmt ./... and golangci-lint run.

[daenney]

Took a look at the tests, it's mad about:

--- FAIL: TestStatusCreateTestSuite (13.14s)

    --- FAIL: TestStatusCreateTestSuite/TestReplyToNonexistentStatus (1.57s)

        statuscreate_test.go:287: 

            	Error Trace:	/drone/src/internal/api/client/statuses/statuscreate_test.go:287

            	Error:      	Not equal: 

            	            	expected: 400

            	            	actual  : 404

            	Test:       	TestStatusCreateTestSuite/TestReplyToNonexistentStatus

        statuscreate_test.go:293: 

            	Error Trace:	/drone/src/internal/api/client/statuses/statuscreate_test.go:293

            	Error:      	Not equal: 

            	            	expected: "{\"error\":\"Bad Request: cannot reply to status that does not exist\"}"

            	            	actual  : "{\"error\":\"Not Found: target status not found\"}"

            	            	

            	            	Diff:

            	            	--- Expected

            	            	+++ Actual

            	            	@@ -1 +1 @@

            	            	-{"error":"Bad Request: cannot reply to status that does not exist"}

            	            	+{"error":"Not Found: target status not found"}

            	Test:       	TestStatusCreateTestSuite/TestReplyToNonexistentStatus

[daenney]

So, for HTTP 400, the spec says:

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

I think the 404 is probably more semantically correct in this case?

[tsmethurst]

Just the one comment, otherwise looks like a good fix :)