Add basic Project view lifecycle operations to the Projects tools

[zwick]

Problem

The GitHub MCP Projects tools can manage projects, fields, items, and status updates, but do not expose Project view lifecycle operations. Agents therefore need to fall back to lower-level API calls.

Scope

Extend the existing Projects tool surface with basic view lifecycle support:

• List and get Project views.
• Create a view with name and layout.
• Update name, layout, and saved filter.
• Delete a view.
• Consider create-time visible_fields where supported by a generally available public endpoint.
• Preserve existing Projects auth, pagination, response, and error conventions.
• Measure tool-schema/token impact and validate against the real GitHub API.

Non-goals

• Grouping, vertical grouping/swimlanes, sorting, slicing, or roadmap settings.
• Depending on preview headers or undocumented API behavior.
• Unrelated Project item-listing reliability fixes.

Acceptance criteria

• An agent can discover and perform the supported lifecycle without writing raw GraphQL.
• Existing Projects tool conventions and authorization behavior are preserved.
• Schema/token impact and targeted eval evidence accompany the change.
• Live API validation covers create, update/filter, read-back, and cleanup using generally available APIs.