[AIRFLOW-5915] Add support for the new documentation theme

[mik-laj]

Make sure you have checked all steps below.

Jira

• My PR addresses the following Airflow Jira issues and references them in the PR title. For example, "[AIRFLOW-XXX] My Airflow PR"
  • https://issues.apache.org/jira/browse/AIRFLOW-5915
  • In case you are fixing a typo in the documentation you can prepend your commit with [AIRFLOW-XXX], code changes always need a Jira issue.
  • In case you are proposing a fundamental code change, you need to create an Airflow Improvement Proposal (AIP).
  • In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

Description

• Here are some details about my PR, including screenshots of any UI changes:

Tests

• My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

• My commits all reference Jira issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":
  1. Subject is separated from body by a blank line
  2. Subject is limited to 50 characters (not including Jira issue reference)
  3. Subject does not end with a period
  4. Subject uses the imperative mood ("add", not "adding")
  5. Body wraps at 72 characters
  6. Body explains "what" and "why", not "how"

Documentation

• In case of new functionality, my PR adds documentation that describes how to use it.
  • All the public functions and the classes in the PR contain docstrings that explain what it does
  • If you implement backwards incompatible changes, please leave a note in the Updating.md so we can assign it to a appropriate release

[codecov-io]

Codecov Report

Merging #6563 into master will decrease coverage by 0.23%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #6563      +/-   ##
==========================================
- Coverage   83.53%   83.29%   -0.24%     
==========================================
  Files         645      645              
  Lines       37286    37291       +5     
==========================================
- Hits        31147    31063      -84     
- Misses       6139     6228      +89

Impacted Files	Coverage Δ
airflow/kubernetes/volume_mount.py	44.44% <0%> (-55.56%)	⬇️
airflow/kubernetes/volume.py	52.94% <0%> (-47.06%)	⬇️
airflow/kubernetes/pod_launcher.py	45.25% <0%> (-46.72%)	⬇️
airflow/kubernetes/refresh_config.py	50.98% <0%> (-23.53%)	⬇️
...rflow/contrib/operators/kubernetes_pod_operator.py	77.14% <0%> (-21.37%)	⬇️
airflow/jobs/local_task_job.py	85% <0%> (-5%)	⬇️
airflow/ti_deps/deps/pool_slots_available_dep.py	95.65% <0%> (-4.35%)	⬇️
airflow/configuration.py	89.13% <0%> (-3.63%)	⬇️
airflow/utils/dag_processing.py	57.99% <0%> (-0.33%)	⬇️
airflow/kubernetes/pod_generator.py	94.69% <0%> (ø)	⬆️
... and 10 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f2473b3...2b1de0b. Read the comment docs.

[kaxil]

? Unnecessary space?

[mik-laj]

This is what the licenses look like in the other files. This license was added automatically and I had no influence on its content.
https://github.com/apache/airflow/blob/master/airflow/www/static/js/base.js
https://github.com/apache/airflow/blob/master/airflow/www/static/js/connection_form.js
https://github.com/apache/airflow/blob/master/airflow/www/static/js/datetime-utils.js
https://github.com/apache/airflow/blob/master/airflow/www/static/js/gantt-chart-d3v2.js
https://github.com/apache/airflow/blob/master/airflow/www/static/js/graph.js

Definition of comment style is available here:

airflow/.pre-commit-config.yaml

Line 66 in 2b1de0b

- "/**| *| */"

[kaxil]

In that case, all good

[potiuk]

Yeah. It's how it should be for consistency :).

[potiuk]

Yeah. It's how it should be for consistency :).

[ashb]

What license is bootstrap released under? Is it right to put an ASF header on it?

[mik-laj]

Bootstrap is under MIT license. We are modifying its source code, so we need to have a header. If we imported correctly, i.e. using SCSS, and the code as an import to external libraries. We would not have this code in this form. Now we have a de facto fork of this library, so we need to have header.