core: swap order of "n_storage_fds" and "n_socket_fds" parameters
    
    When process fd lists to pass to activated programs we always place the
    socket activation fds first, and the storage fds last. Irritatingly in
    almost all calls the "n_storage_fds" parameter (i.e. the number of
    storage fds to pass) came first so far, and the "n_socket_fds" parameter
    second. Let's clean this up, and specify the number of fds in the order
    the fds themselves are passed.
    
    (Also, let's fix one more case where "unsigned" was used to size an
    array, while we should use "size_t" instead.)
    
    (cherry picked from commit 25b583d7ffd699384435eba8e49f6ce927a83af0)
    
    Resolves: #1683334
    
    patch_name: 0191-core-swap-order-of-n_storage_fds-and-n_socket_fds-pa.patch
    present_in_specfile: true
    location_in_specfile: 191
    squash_commits: true