Use the GrDirectContext factories instead of deprecated GrContext ones

[Adlai-Holler]

This is part of a larger effort to expose the difference between GrDirectContext, which runs on the GPU thread and can directly perform operations like uploading textures, and GrRecordingContext, which can only queue up work to be delivered to the GrDirectContext later.

Over time, GrContext will be replaced by:

• GrDirectContext in cases where we know that we have the GPU access / with functions that require it.
• GrRecordingContext in cases where we aren't sure / with functions that do not need to perform such actions.
  • In practice, since Flutter plumbs the context around on its own (say, instead of using SkCanvas->recordingContext,) we pretty much have the direct context handy at all times.

Rough outline of what's going on is here. The key is SkDeferredDisplayLists – when dealing with them, which Flutter does not presently, the GrContext is actually incapable of talking to the GPU because it's not on the GPU's thread. Right now, the internal GrDDLContext you get just stubs off functionality that it can't perform, but this won't scale – we need to reveal this distinction to users so they can be clear about what's allowed and what's not.

[Adlai-Holler]

The remaining failures seem like a tooling issue? <vulkan.h> file not found.

@jason-simmons @gaaclarke thoughts on this? It's a big CL and I'm happy to talk more about the reason for it, but we'll have to do it eventually so we might as well rip the bandaid off. There's other API changes coming that are currently blocked by this (for instance, SkImage::MakeCrossContextFromPixmap should take a GrDirectContext argument instead of a GrContext one.

[jason-simmons]

@chinmaygarde

[Adlai-Holler]

Hi Chinmay! It's been about 6 years, I think!

[gaaclarke]

Hey @Adlai-Holler , can you link to the documentation about the deprecation of GrContext in the description of the issue?

As for the vulkan.h not found problem. I'm not sure what the problem is there. It's probably best to file an issue about it and add // FLUTTER_NOLINT at the top of the file (directly below the copyright) for now until it can be debugged.

[Adlai-Holler]

Thanks for the reply! I've added the NOLINT. Where should I file an issue? This repo doesn't seem to support them.

[chinmaygarde]

Hey! small world.

Thanks for the background. This should only affect Flutter once it starts building its own DDLs.

[chinmaygarde]

Where should I file an issue?

https://github.com/flutter/flutter/issues/new

[Adlai-Holler]

Issue filed at flutter/flutter#62222

Looks like we have only infra failures remaining on the CI.

[gaaclarke]

@Adlai-Holler I had those problems with CI yesterday. I haven't been able to verify if it is fixed now but rebasing your PR onto master should fix it.

edit: Don't even worry about it. Once this gets through review we can rebase before we land.

[Adlai-Holler]

Rebased

[Adlai-Holler]

build_and_test_linux_unopt_debug failure seems like an infra flake

[Adlai-Holler]

@gaaclarke @chinmaygarde Any chance we can get this in the bank today?

[chinmaygarde]

The web stuff is unrelated and it seems to be referencing the framework which was broken at the time of the presubmit run. I am landing this now.