Fixed custom fieldset order

[Godmartinz]

Description

Custom Fieldsets order would start at zero, they now start at 1.

Before:

After:

Fixes #sc-19126

Type of change

Please delete options that are not relevant.

• [x ] Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

• Test A
• Test B

Test Configuration:

• PHP version:
• MySQL version
• Webserver version
• OS version

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[shortcut-integration]

This pull request has been linked to Shortcut Story #19126: Custom fields order display is wonky.

[what-the-diff]

PR Summary

• Enhanced Field Order Display
  The counting of the field order in a certain view page was updated so instead of starting from the initial value, it will begin with the initial value plus one. This makes it more intuitive for users who are more familiar with counting starting from one instead of zero.

[snipe]

This seems like a bit of a cheat, but I'll take it ;)