Add slice initialization to avoid null response

[seedspirit]

Proposed changes

In some APIs that retrieve multiple entities, if there are no entities that meet the conditions, the API returns null instead of an empty list. To ensure consistent response format, we modified the code to initialize empty slices before processing the results.

Before

After

About Frontend

As frontend use optional chaining to safely handle null response(or not used in anywhere in case of projectStats), this change won't affect the frontend behaivor

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

[S-ayanide]

LGTM