Draft: Expose timelogs against projects in graphql

What does this MR do?

We currently expose Timelogs against Group(s), MergeRequest(s) and Issue(S)... but should also expose against Proejct(s) to facilitate reporting requirements (see !60161 (merged) for the first incarnation of reporting at issuable level).

This MR adds the Timelogs field to the graphQL ProjectType

Screenshots (strongly suggested)

query {
  project(fullPath: "twitter/Typeahead.Js") {
    id
    name
    timelogs(startDate: "2021-03-01" endDate: "2021-03-30") { nodes { 
        timeSpent
        issue { id }
        note { body } 
    } }
  }
}

{
    "data": {
        "project": {
            "id": "gid://gitlab/Project/7",
            "name": "Typeahead.Js",
            "timelogs": {
                "nodes": [
                    {
                        "timeSpent": 300,
                        "issue": null,
                        "note": {
                            "body": "A note with some time"
                        }
                    }
                ]
            }
        }
    }
}

Does this MR meet the acceptance criteria?

Conformity

• 📋 Does this MR need a changelog?
  • I have included a changelog entry.
  • I have not included a changelog entry because _____.
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team