[service] V2 migration linter - checks to add

[SSE4]

now we have V2 migration linter (#11147), it's time to think about useful checks to add.
we definetely don't want to add too broad checks like replace "import conans" via "import conan", as it basically means "rewrite the whole recipe".
I personally guess we should start from small things, which are easy to check and fix.
a good candidates where should we start could be:

1. V2 migration guide - it lists some useful things, but definetely, it still lacks a lot of things.
2. learn from our own expirience. e.g. fmt migration highlights some major things to be done

from what I can currently recommend, we may try to implement the following pieces first:

1. easy imports (existing in both v1 and v2), like from conan.errors import ConanInvalidConfiguration, from conan import ConanFile, with higher granularty
2. replace run_environment=True via env="conanrun" (VirtualRunEnv generator)
3. use self.info in package_id method instead of just self
4. use conan.tools instead of conan.tools, with higher granularity - code changes are mostly to add first self argument, but they are in different namespaces now
5. replace build_requires via tool_requires
6. enforce explicit test_type

anything else?

[uilianries]

I would say conan-io/hooks#387 is related. Adding set_property would be great too.

[jgsogo]

Whatever can be easily fixed by any contributor seeing the error, it is more than welcome. Anyone should feel free to suggest the changes to the linter, the PR will validate how many recipes are broken given the new check and the merge might be blocked if there are too many errors.

[Croydon]

I guess this issue can be closed.

The most basic check is no imports from conans.* and then let's see if 2.0 CI succeeds.

Otherwise this is more an issue for the hooks repository, right?

[valgur]

@uilianries Can probably close this one as well.