Add environment file to GitHub workflows

[antonwolfy]

TBC

• Have you provided a meaningful PR description?
• Have you added a test, reproducer or referred to issue with a reproducer?
• Have you tested your changes locally for CPU and GPU devices?
• Have you made sure that new changes do not introduce compiler warnings?
• Have you checked performance impact of proposed changes?
• If this PR is a work in progress, are you filing the PR as a draft?

[github-actions]

View rendered docs @ https://intelpython.github.io/dpnp/pull/2258/index.html

[AlexanderKalistratov]

Is environment.yml missing?

[antonwolfy]

It's generating by the command:

conda-merge ${{ env.base-doc-env }} ${{ env.build-pkgs-env }} > ${{ env.environment-file }}

[AlexanderKalistratov]

Cool. Do we need to hardcode python=3.12 dependency in base_duild_docs.yml ?

Taking into consideration that we can dynamically create environment files using conda-merge?

Or am I missing something?

[antonwolfy]

The file will be split later, because part of packages are common with coverage workflow.
The PR is work in progress still :)

In general, the python is pinned as 3.12, because cupy package doesn't support 3.13, i.e. max python version depends on cupy package and so I linked them there in one file.

Alternatively we can miss python in base_duild_docs.yml and to pass as option of conda-incubator/setup-miniconda step, but I preferred to do that through base_duild_docs.yml file.

[coveralls]

coverage: 70.844%. remained the same
when pulling 469f633 on stabilize-public-ci-part-3
into 807179a on master.

[github-actions]

View rendered docs @ https://intelpython.github.io/dpnp/pull/2258/index.html

[github-actions]

Array API standard conformance tests for dpnp=0.17.0dev4=py312he4f9c94_11 ran successfully.
Passed: 950
Failed: 0
Skipped: 50