Add strippedSafeToJSON

[mchaver]

#36

[Vlix]

Thank you for the PR! 🙏

I'll try to review this more seriously in the next month.

[Vlix]

Also please update the package.yaml's version to 1.2.1.0

[Vlix]

I feel these functions should be added under the Version section. The context there makes more sense and would be better when describing why these functions exist.

    , Version
    , noVersion
    , setVersion
    , setVersion'
    , getVersion
    -- *** Removing the 'SafeJSON' version
    --
    -- | Sometimes you might want (or need) to produce JSON without `SafeJSON` versioning.
    --   Maybe you don't want to leak internals to third parties, or the version fields are
    --   irrelevant and only clutter in a specific instance.
    --   Regardless of the case, if you don't need to parse the JSON again, these functions
    --   can be used to remove the `SafeJSON` versioning.
    , removeVersion
    , strippedSafeToJSON
    , strippedEncode

And then we'll give a bit more context per function.

[Vlix]

This would be a minor version increase. 1.2.1.0

[Vlix]

-- | 'safeToJSON' without any `SafeJSON` versioning.
--   Effectively the same as 'Data.Aeson.toJSON', but using the 'safeTo' method.
--
--   Sometimes you don't need (or want) the versioning, so if you don't need to parse
--   the 'Data.Aeson.Value' later on, this is a convenience function to easily 
--   remove the version fields from the resulting JSON. 
-- 
-- @
-- strippedSafeToJSON = 'removeVersion' . 'safeToJSON'
-- @
-- 
-- @since 1.2.1.0

[Vlix]

-- | Encode a 'SafeJSON' value to a 'LBS.ByteString' without SafeJSON versioning.
--
--   Like this package's own 'Data.Aeson.Safe.encode' function,
--   but without version fields in the resulting 'LBS.ByteString'.
--
-- @
-- strippedEncode = 'Data.Aeson.encode' . 'strippedSafeToJSON'
-- @
-- 
-- @since 1.2.1.0

[Vlix]

Oh, and rebase onto master, please. The CI has been fixed.