Integer arrays serialized as strings in changelog snapshot

[jeremystretch]

NetBox version

v3.2.1

Python version

3.8

Steps to Reproduce

1. Create a service with all required parameters. Set the ports to 80, 8080.
2. View the creation record in the service's change log

Expected Behavior

The list of designated ports (which are stored on the model as an array of integers) should be recorded as ports: [80, 8080].

Observed Behavior

The ports are serialized as a string: ports: "[\"80\", \"8080\"]".

This seems to be a limitation of Django's built-in JSON serializer, which apparently does not support array types.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

[arthanson]

Created a Django issue: https://code.djangoproject.com/ticket/33974

[arthanson]

Closed as wontfix in Django: "Thanks for the report however (de-)serialization works for me with
ArrayField(base_field=models.PositiveSmallIntegerField()). Are there any
practical issues with the current approach (except for your preferences)?
Other complex fields (such as JSONField) are also serialized as strings.
I'm afraid that the proposed change is backward incompatible and you can
always use a custom serializer, if you need a different format."

Will do a workaround.

[arthanson]

I see two potential ways to fix:

1. Create a new field subclassing an Integer ArrayField that has a value_to_string that will do the correct serialization. Would not only change the change log but also Fixtures (not sure if this would be any issue). Would potentially create a new. migration unless it gets weeded out.
2. Just change it in the change log serialization code, that field can be popped out of the standard serializer and then serialized correctly. Would only effect the change log codepath.

@jeremystretch I'm leaning towards 1 unless there are side-effects I'm not aware of or you have a preference?