Allow plugin name in is_plugin_enabled

[pfertyk]

Fixes #61604.

[akien-mga]

There's also set_plugin_enabled which likely has the same issue. And the documentation is still incorrect as it now mentions only one of the supported formats, but not both.

IMO, it would be better if only the plugin name was supported (i.e. like the docs), the fully qualified path is not a useful format for this API.

Which means that #43734 should be reworked to make sure that it doesn't regress for the case it implemented.

[pfertyk]

I've changed the other method as well ;) For now, both support path and name. Let me know if I should change it to name only, or change the docs :)

I'm traveling now, but next week I'll have more time to take a look at #43734 to see if I've missed something ;)

[akien-mga]

This is fine to fix the regression for now but I think this still needs more work, it's a super weird API that requires passing a fully qualified path to the plugin.cfg, and the docs are not reflecting this well.

[akien-mga]

Thanks!

[akien-mga]

This doesn't seem relevant for 3.x which already had this issue fixed in #46389. For some reason this was not forward ported to master. @KoBeWi you mentioned the bug affected 3.5, can you check again?

[KoBeWi]

Indeed, the issue doesn't happen in 3.5. I incorrectly assumed that it's relevant for this version, because I forgot it was fixed .-.