feat: add null option and rewrite README

[fahchen]

Summary

• Add null option for field types to control nullability explicitly
• Rewrite README for clarity and conversational tone

Changes

New null option

Fields can now use null: false to prevent nil from being added to their type, or null: true (default) to allow it. This is useful for database records where some fields are always present (like id, inserted_at).

typed_structor do
  field :id, integer(), null: false       # Never nil
  field :name, String.t(), null: true     # Always nullable
end

The option can also be set at the module level:

typed_structor null: false do
  field :id, integer()                    # Not nullable by default
  field :phone, String.t(), null: true    # Override for this field
end

README rewrite

• Added "Why TypedStructor?" section with before/after comparison
• Reorganized content into logical sections (Getting Started, Options, Common Patterns, Advanced Features)
• Made examples more practical and self-contained
• Improved formatting with callouts and tables

Changelog

- feat: add null option for field types
- docs: rewrite README for clarity and conversational tone

[Copilot]

Pull request overview

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

This comment could be misleading. The test demonstrates that fields can be nil at runtime even with null: false (line 47), not just "nullable fields". Consider revising to clarify that the null option only affects the type specification, not runtime behavior. For example: "Fields can hold nil at runtime regardless of null option".

Suggested change

	# Struct can be created with nil for nullable fields
	# Struct fields can be nil at runtime regardless of null option in the type spec