get_blogs_of_user should not set archived, spam and delete to 0

[realloc]

get_blogs_of_user creates blog-objects and adds them to an array right after a call of get_blog_details. It uses all data of that function but sets the properties archived, spam and delete to 0 even if this is not true.

[realloc]

Patch and unit-test

[jeremyfelt]

Hi @realloc, thanks for the ticket and patch and tests!

At first glance, this seems to make sense. I'm not sure that we have any other reasoning for setting everything to 0 other than something was necessary to avoid notices (see #16225). Otherwise, the same method of providing data has existed since [15671].

I'm going to bump this to 4.3, but sit on it for a bit to make sure we're not missing anything.

[jeremyfelt]

In 32626:

Provide all site flag data in objects returned by get_blogs_of_user()

Previously, archived, spam, and deleted properties were forced to 0 when returned by get_blogs_of_user(). This was originally introduced in [21794] as a way to prevent notices when properties were expected.

Instead, we can properly fill these properties with those retrieved from get_blog_details().

Props realloc.
Fixes #32281.