fix(filter.numeric_filter): Prefer filter.type in the spread operation

[AlexanderGeere]

Description

Filter types were being overwritten by the type of the entry due to this line:

in lib/ui/layers/filters.mjs. This meant that setting the filter type to numeric or integer would always use numeric steps e.g. 0.01
as the type of the filter would the same as the entry, text for example, and steps would default:

This PR uses a spread operation filter to entry to maintain the filters' type.

GitHub Issue

#2895

Type of Change

• ✅ Bug fix (non-breaking change which fixes an issue)
• ✅ Documentation

How have you tested this?

Tested locally

Important

bugs_testing/filter/all_filters.json
The numeric filter should use decimal steps and the integer filter should use integer steps

Testing Checklist

• ✅ Existing Tests still pass
• ✅ Ran locally on my machine

Code Quality Checklist

• ✅ My code follows the guidelines of XYZ
• ✅ My code has been commented
• ✅ Documentation has been updated
• ✅ New and existing unit tests pass locally with my changes
• ✅ Main has been merged into this PR

[simon-leech]

Working for me - tested overwriting the title and type of filter and all good! 👍

    {
      "title": "UK Rank",
      "field": "rp_rank",
      "fieldfx": "select case when rp_rank is not null then to_char(rp_rank, 'FM999,999,999') || ' of ' ||  1000 else null end",
      "inline": true,
      "skipNullValue": true,
      "filter": {
        "title": "HELLO",
        "type": "integer"
      }
    },

[dbauszus-glx]

I quickly revised the documentation. I highly recommend using inline copilot for this kind of things to make sure that missing properties are documented.