Replace int spy in `romamNumeral` test

[ST-DDT]

Why do we need to spy on the int method at all? Can we simply test faker.number.romanNumeral({ min: value, max: value}) and expect the same outcome without having to spy on the implementing function?

Originally posted by @xDivisionByZerox in #3857 (comment)

[itsgintoki]

Hi! I would like to work on this issue.

Proposed approach:
- Locate the tests for `faker.number.romanNumeral` that spy on `faker.number.int`.
- Remove the `vi.spyOn` calls on `int`.
- Refactor the test cases to pass `{ min: value, max: value }` directly into `faker.number.romanNumeral(...)` and assert the expected Roman numeral strings.
- Verify all test suites pass with `pnpm test`.

Could you please assign this to me?

[ST-DDT]

Sure, go ahead.