[iOS & tvOS] ItemLibraryViewModel - Cleanup

[JPKribs]

Summary

The goal of this. PR is to touch up the ItemLibraryViewModel to accommodate some of the new items that we've added since it was created. @LePips left some notes in in there and ItemTypeLIbraryViewModel and mostly I am going to try and follow them.

Primary change was I removed ItemTypeLIbraryViewModel and moved ItemType to the the ItemFilterCollection instead. I've tested on tvOS and all libraries are correct including the the ItemType sections for TV Shows and Movies. Because of this, we are still able use a single ViewModel for both existing Library types we have on iOS and tvOS.

This PR is based on: #1409 (review)

[JPKribs]

@LePips This all looks correct and is working as intended. Please let me know if there is anything that I should be doing differently or if you had any other cleanup intended! The only missing item I'd like to roll into this PR is from ItemLibraryViewModel.

I was looking at adding this (see below) but might need a bit more context. Since LibraryParent is a protocol, do we want that there? Or on the enum for libraryType? Or a LibraryParent func in ItemLibraryViewModel?

    func itemParameters(for page: Int?) -> Paths.GetItemsByUserIDParameters {

        var libraryID: String?
        var personIDs: [String]?
        var studioIDs: [String]?
        var isRecursive: Bool? = true

        // TODO: this logic should be moved to a `LibraryParent` function
        //       that transforms a `GetItemsByUserIDParameters` struct, instead
        //       of having to do this case-by-case.

        if let libraryType = parent?.libraryType, let id = parent?.id {
            switch libraryType {
            case .collectionFolder, .userView:
                libraryID = id
            case .folder:
                libraryID = id
                isRecursive = nil
            case .person:
                personIDs = [id]
            case .studio:
                studioIDs = [id]
            default: ()
            }
        }

        var parameters = Paths.GetItemsByUserIDParameters()
        parameters.enableUserData = true
        parameters.fields = .MinimumFields
        parameters.isRecursive = isRecursive
        parameters.parentID = libraryID
        parameters.personIDs = personIDs
        parameters.studioIDs = studioIDs
        ...

---

One unintended side effect of using the includeItemTypes for the filters is they were previously set defaulted to [.movie, .series, .boxSet] for all ItemLibraryViewModel. I added a ItemLibraryViewModel default to [.movie, .series, .boxSet] that are used if the FilterViewModel is not present. FilterViewModel defaults to [.movie, .series, .boxSet] as well so if there is a library that does not specifically set a type this will use the previous values as well.

[JPKribs]

I am adding this to mirror iOS.

[JPKribs]

This does 2 things:

1. Right now, when filters are not present, there is no sort order. For an example, take the current 1.2 or 1.3(5) version and open select a person. It will show you all of their movies & shows but in no specific order. This is because the order is set from the FilterViewModel. This ensure, if the FilterViewModel is not present, this will default to ordering the results by name.

2. Since I am using the includeItemTypes in the FilterViewModel, I don't want to set this value twice, This [.movie, .series, .boxSet] is the previously default value for this, so I am ensuring this is set when a FilterViewModel is not present (see people again). This is the same default found on the FilterViewModel so it will be set there as well if the view does not use these values.

The alternative to this is I can reference FilterViewModel.init().currentFilters.types so this is only being set from the FilterViewModel?