timesheet scenarios

• 556-should-create-time-sheet-row-and-check-headers-across-weeks — Should create time sheet row and check headers across weeks
• 557-should-create-time-sheet-row-and-check-headers-in-past-weeks — Should create time sheet row and check headers in past weeks
• 558-should-copy-multi-row-sheet-to-next-week-with-all-configurations-preserved — Should copy multi-row sheet to next week with all configurations preserved
• 559-trashing-the-row-s-project-removes-it-from-the-timesheet — Trashing the row's project removes it from the timesheet
• 560-should-copy-row-to-next-week-after-deleting-its-task — Should copy row to next week after deleting its task
• 561-should-copy-row-to-next-week-after-deleting-its-client — Should copy row to next week after deleting its client
• 562-should-reject-creating-rows-with-duplicate-configuration — Should reject creating rows with duplicate configuration
• 563-should-allow-same-client-different-labels — Should allow same client + different labels
• 564-should-distinguish-billable-vs-non-billable-as-different-rows — Should distinguish billable vs non-billable as different rows
• 565-should-create-multiple-rows-and-delete-one — Should create multiple rows and delete one
• 566-should-aggregate-api-created-time-records-into-the-matching-timesheet-rows — Should aggregate API-created time records into the matching timesheet rows
• 567-should-create-two-rows-add-time-records-mirror-in-calendar-then-delete-one-row — Should create two rows, add time records, mirror in calendar, then delete one row
• 568-should-split-a-hours-h-time-record-across-consecutive-days — Should split a ${hours}h time record across consecutive days
• 569-should-populate-mirror-and-edit-several-rows-of-time-records-then-delete-one — Should populate, mirror, and edit several rows of time records, then delete one