OpenCL suite

# Open Effects Proposal for Standard Change

Please read the contribution [guidelines](https://github.com/ofxa/openfx/wiki/Extending-OpenFX-Guidelines#submit-a-proposal-or-bug-report-to-review) first.

## Standard Change Workflow
- [X ] Create proposal as issue (you're doing this now!)
- [x] Tag this issue with `standard change` tag
- [ ] Identify subcommittee: at least one plug-in vendor, and at least one host
- [ ] Discuss the idea in this issue
- [ ] Write new or updated code and doc
- [ ] Publish updates as a pull request (ideally on a `feature/PROPOSAL-NAME` branch)
- [ ] Make sure that PR references this issue number to keep them in sync
- [ ] Discuss and review code in the PR
- [ ] Meet all requirements below for accepting PR
- [ ] When subcommittee signs off and other members don't have any further review comments,
maintainer merges PR to master which closes PR and issue

## Requirements for accepting a standard change:
- [ ] Header files updated
- [ ] Documentation updated
- [ ] Release notes added
- [ ] Compatibility review completed
- [ ] Working code demonstrated with at least one host and one plugin
- [ ] At least two members sign off
- [ ] No further changes requested from membership

## Summary

Can someone make a pull request against this for OpenCL suite proposal. It's fine to add WIP so we understand it's for reference review.

## Motivation

We are waiting for a while for this to be able to abstract GPU API and be able to decide what we do with VK, Metal,.... It should be OCL 3.0 compliant too now :)

## Problem

Certain hosts (like those who support multi-GPU on Windows GTX/RTX cards) cannot support the OpenGL suite, another API is necessary to allow that.

## Impact

The preliminary suite has been reviewed by 3 members.

## Documentation Impact

A new header file would be added.

## Stakeholders

ALL

## Discussion

Start with the linked OpenFX contribution guidelines and review the standard-change workflow in this issue. Identify the preliminary OpenCL suite proposal and the existing suite headers it must align with. Done requires a reviewed pull request covering the header, documentation, release notes, compatibility review, and working host/plugin demonstration, with two member sign-offs.

Written by the indexing model from the issue text.