feat!: update data type in ResourceProperties

[chr1shung]

BREAKING CHANGE: update mask,shift,base,scale,offset to numeric data type

also rename 'Others' to 'Optional' for the consistency with message broker settings.

closes #770

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/go-mod-core-contracts/blob/main/.github/Contributing.md

PR Checklist

Please check if your PR fulfills the following requirements:

• I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
• I am not introducing a new dependency (add notes below if you are)
• I have added unit tests for the new feature or bug fix (if not, why?)
• I have fully tested (add details below) this the new feature or bug fix (if not, why?)
• I have opened a PR for the related docs change (if not, why?)

Testing Instructions

New Dependency Instructions (If applicable)

[codecov-commenter]

Codecov Report

Merging #809 (9353c25) into main (7d700bc) will not change coverage.
The diff coverage is 50.00%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

@@           Coverage Diff           @@
##             main     #809   +/-   ##
=======================================
  Coverage   64.60%   64.60%           
=======================================
  Files          80       80           
  Lines        3099     3099           
=======================================
  Hits         2002     2002           
  Misses        908      908           
  Partials      189      189           

Impacted Files	Coverage Δ
dtos/resourceproperties.go	50.00% <50.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[lenny-goodell]

LGTM

[iain-anderson]

Can we use json.Number for scale, offset and base - so that they can be integer or float?

[chr1shung]

Can we use json.Number for scale, offset and base - so that they can be integer or float?

json.Number is alias of string which provides useful methods to transform value to numeric data type.
But there still will be error in the same place if user provides illegal value:
https://github.com/edgexfoundry/device-sdk-go/blob/b46b419fd49731d0deb4deed8e6127ef6a42900c/internal/transformer/transformresult.go#L92-L93

Using float64 directly can avoid the error during device profile creation but it's a breaking change.

Another way to improve this is to use json.Number for these properties, but leverage validator to check the type.
For example https://pkg.go.dev/github.com/go-playground/validator/v10#hdr-Numeric for base, scale and offset.
But we might need to implement custom tag for mask(uint) and shift(int)

@lenny-intel @cloudxxx8 @iain-anderson thought ?

[cloudxxx8]

@iain-anderson is it ok?

[iain-anderson]

OK with this as is