fix: Respect schema names in short FlexNamer

[TheAwiteb]

Fixes #833

Changes

In this PR, I addressed the issue where FlexNamer did not respect the schema
name when generating the short name. Previously, FlexNamer incorrectly used
the type_name parameter as the short name in the Force rule. This has been
corrected by using the force_name parameter as the short name in the Force
rule.

Note

This fix only applies to the schema name itself and does not address cases where
the schema name is used as a generic type. Unfortunately, this limitation cannot
be resolved, so please avoid naming your schema if it is intended for use as a
generic type.

Screenshot

This screenshot shows the updated FlexNamer implementation

Before

After

[TheAwiteb]

Hey @chrislearn, is the test_derive_to_schema_generics test written incorrectly? I noticed that there are aliases for i32 and String, but they are not on the right-hand side of the assertion. The new left-hand side is below. Should I fix the right-hand side, or am I missing something?

{
  "MyI32": {
    "properties": {
      "value": {
        "format": "int32",
        "type": "integer"
      }
    },
    "required": [
      "value"
    ],
    "type": "object"
  },
  "MyObject_u64_": {
    "properties": {
      "value": {
        "format": "int64",
        "minimum": 0,
        "type": "integer"
      }
    },
    "required": [
      "value"
    ],
    "type": "object"
  },
  "MyStr": {
    "properties": {
      "value": {
        "type": "string"
      }
    },
    "required": [
      "value"
    ],
    "type": "object"
  }
}