Refactor: Seeder, views, and migrations for consistency

[thejmitchener]

Pull Request Description: Refactor: Seeder, Views, and Migrations for Consistency

This pull request introduces significant refactoring across several components of the project, including the seeder, migrations, and views, to enhance consistency and maintainability.

Motivation for the Change

1. Improved Naming Conventions:

   • The renaming of the image field to feature_image in the migration aligns better with common practices and improves clarity about its purpose.
   • The seeder class has been renamed from PagesTableSeeder to PageTableSeeder to maintain singular naming conventions, thereby enhancing readability and consistency across the codebase.

2. Standardized View Components:

   • The updates in the Blade templates ensure a more consistent application of classes and attributes. This includes unifying the text color for better contrast and accessibility, which enhances the user experience.

3. Enhanced Factory Usage:

   • The introduction of the PageFactory allows for easier and more flexible generation of test data, which is crucial for maintaining robust unit tests and ensuring accurate database interactions.

4. SEO Improvements:

   • The refactoring improves the way SEO data is passed to views, using a more streamlined approach that reduces redundancy and enhances performance.

Benefits to the Project

• Consistency: By standardizing naming conventions and practices across the project, we reduce cognitive load for developers and make it easier to navigate the codebase.
• Maintainability: Cleaner and more consistent code is easier to maintain and extend, facilitating future development efforts.
• Improved Readability: Clearer naming and structured views enhance the readability of the code, making it easier for new contributors to onboard and understand the existing architecture.
• Enhanced Performance: Optimized view handling can lead to better performance in rendering and serving pages, which is crucial for user experience.

Overall, these changes are aimed at fostering a more organized and efficient codebase, ultimately leading to a more robust and scalable application.