Data Migration: pageobjects migration to SQL-based versions

[DhiraPT]

Add SQL-based versions of pageobject classes to support E2E test migration.

• Abstract out methods into new SQL-based classes.

• Do not combine SQL-based code with old Datastore-based code in the same class.

Task List: Migrate PageObjects to SQL-based versions (only classes that need migration)

• AdminSearchPage

• AppPage (retain existing name)

• FeedbackResultsPage

• FeedbackSubmitPage

• InstructorCourseDetailsPage

• InstructorCourseEditPage

• InstructorCourseEnrollPage

• InstructorCoursesPage

• InstructorCourseStudentDetailsEditPage

• InstructorCourseStudentDetailsViewPage

• InstructorFeedbackEditPage

• InstructorFeedbackResultsPage

• InstructorFeedbackSessionsPage

• InstructorHomePage

• InstructorSearchPage

• InstructorSessionIndividualExtensionPage

• InstructorStudentListPage

• InstructorStudentRecordsPage

• StudentCourseDetailsPage

• UserNotificationsPage

[twhjames]

@DhiraPT Hi! May I attempt to contribute to this PR for InstructorFeedbackResultsPage?

[DhiraPT]

@twhjames Yes, sure!

[DhiraPT]

@myrilla12 Yes, thank you!

Also for @twhjames, some tips for the migration:

1. Copy the entire old pageobject to the new file and then add "Sql" to the file name and class name.
2. Remove the imports from teammates.common.datatransfer.attributes (so we can easily see which entity to replace).
3. Replace all the entity with their sql entity (e.g. StudentAttributes to Student).
4. Remove any non-sql methods from the new class (e.g., methods that only apply to Attributes) and remove sql-related methods from the old class.
5. Update any sql test classes that are using the old pageobject.

These are just some of the basic tips. Sometimes you may need additional adjustments, so I would recommend understanding the existing logic first (what the class does and how it is being used). Maybe you can also uncover some hidden bugs in the current implementation.