Fix id names in rst renders after docutils 0.18

Fix id names changing in rst renders with the upgrade to docutils 0.18
by enforcing the old default value `id` for `auto_id_prefix`.

See: https://docutils.sourceforge.io/RELEASE-NOTES.html#release-0-18-2021-10-26

co-authored-by: Tyler Dixon <tylerdixon@github.com>

Author: pudiva

lib/github/commands/rest2html

@@ -160,6 +160,7 @@ SETTINGS = {
     'syntax_highlight': 'none',
     'math_output': 'latex',
     'field_name_limit': 50,
+    'auto_id_prefix': 'id',
 }
 
 default_highlight_language = None

test/markups/README.long.rst.html

@@ -46,7 +46,7 @@ <h1>Robot Framework 7.0</h1>
 </ul>
 </div>
 <a name="installation"></a>
-<h2><a href="#toc-entry-1">Installation</a></h2>
+<h2><a href="#id113">Installation</a></h2>
 <p>If you have <a href="http://pip-installer.org">pip</a> installed, just run</p>
 <pre>
 pip install --upgrade robotframework
@@ -59,7 +59,7 @@ <h2><a href="#toc-entry-1">Installation</a></h2>
 from <a href="https://pypi.python.org/pypi/robotframework">PyPI</a> and install it manually. For more details and other installation
 approaches, see the <a href="../../INSTALL.rst">installation instructions</a>.</p>
 <a name="most-important-enhancements"></a>
-<h2><a href="#toc-entry-2">Most important enhancements</a></h2>
+<h2><a href="#id114">Most important enhancements</a></h2>
 <blockquote>
 <p>If you are interested to learn more about the new features in Robot Framework 7.0,
 join the <a href="https://robocon.io">RoboCon conference</a> in February, 2024. <a href="https://github.com/pekkaklarck">Pekka Klärck</a>, Robot Framework
@@ -71,7 +71,7 @@ <h2><a href="#toc-entry-2">Most important enhancements</a></h2>
 used for future Robot Framework development.</p>
 </blockquote>
 <a name="listener-enhancements"></a>
-<h3><a href="#toc-entry-3">Listener enhancements</a></h3>
+<h3><a href="#id115">Listener enhancements</a></h3>
 <p>Robot Framework's <a href="http://robotframework.org/robotframework/latest/RobotFrameworkUserGuide.html#listener-interface">listener interface</a> is a very powerful mechanism to get
 notifications about various events during execution and it also allows modifying
 data and results on the fly. It is not typically directly used by normal Robot
@@ -179,7 +179,7 @@ <h4>Paths are passed to version 3 listeners as <code>pathlib.Path</code> objects
 paths were strings, but nowadays listener version 3 methods get them as
 more convenient <a href="https://docs.python.org/3/library/pathlib.html">pathlib.Path</a> objects.</p>
 <a name="native-var-syntax"></a>
-<h3><a href="#toc-entry-4">Native <code>VAR</code> syntax</a></h3>
+<h3><a href="#id116">Native <code>VAR</code> syntax</a></h3>
 <p>The new <code>VAR</code> syntax (<a href="https://github.com/robotframework/robotframework/issues/3761">#3761</a>) makes it possible to create local variables
 as well as global, suite and test/task scoped variables dynamically during
 execution. The motivation is to have a more convenient syntax than using
@@ -245,7 +245,7 @@ <h3><a href="#toc-entry-4">Native <code>VAR</code> syntax</a></h3>
     IF    1 &gt; 0    VAR    ${x}    true value    ELSE    VAR    ${x}    false value
 </pre>
 <a name="mixed-argument-support-with-library-keywords"></a>
-<h3><a href="#toc-entry-5">Mixed argument support with library keywords</a></h3>
+<h3><a href="#id117">Mixed argument support with library keywords</a></h3>
 <p>User keywords got support to use both embedded and normal arguments in Robot
 Framework 6.1 (<a href="https://github.com/robotframework/robotframework/issues/4234">#4234</a>) and now that support has been added also to library keywords
 (<a href="https://github.com/robotframework/robotframework/issues/4710">#4710</a>). The syntax works so, that if a function or method implementing a keyword
@@ -266,7 +266,7 @@ <h3><a href="#toc-entry-5">Mixed argument support with library keywords</a></h3>
     Number of dogs should be    3
 </pre>
 <a name="json-result-format"></a>
-<h3><a href="#toc-entry-6">JSON result format</a></h3>
+<h3><a href="#id118">JSON result format</a></h3>
 <p>Robot Framework 6.1 added support to <a href="https://github.com/robotframework/robotframework/blob/master/doc/releasenotes/rf-6.1.rst#json-data-format">convert test/task data to JSON and back</a>
 and Robot Framework 7.0 extends the JSON serialization support to execution results
 (<a href="https://github.com/robotframework/robotframework/issues/4847">#4847</a>). One of the core use cases for data serialization was making it easy to
@@ -293,7 +293,7 @@ <h3><a href="#toc-entry-6">JSON result format</a></h3>
 <p>The plan is to enhance the support for JSON output files in the future so that
 they could be created already during execution. For more details see issue <a href="https://github.com/robotframework/robotframework/issues/3423">#3423</a>.</p>
 <a name="argument-conversion-enhancements"></a>
-<h3><a href="#toc-entry-7">Argument conversion enhancements</a></h3>
+<h3><a href="#id119">Argument conversion enhancements</a></h3>
 <p>Automatic argument conversion is a very powerful feature that library developers
 can use to avoid converting arguments manually and to get more useful Libdoc
 documentation. There are two important new enhancements to it.</p>
@@ -340,7 +340,7 @@ <h4>Support  "stringified" types like <code>'list[int]'</code> and <code>'int |
 <p>These stringified types are also compatible with the Remote library API and other
 scenarios where using actual types is not possible.</p>
 <a name="tags-set-globally-can-be-removed-using-tag-syntax"></a>
-<h3><a href="#toc-entry-8">Tags set globally can be removed using <code>-tag</code> syntax</a></h3>
+<h3><a href="#id120">Tags set globally can be removed using <code>-tag</code> syntax</a></h3>
 <p>Individual tests and keywords can nowadays remove tags that have been set in
 the Settings section with <code>Test Tags</code> or <code>Keyword Tags</code> settings by using
 the <code>-tag</code> syntax with their own <code>[Tags]</code> setting (<a href="https://github.com/robotframework/robotframework/issues/4374">#4374</a>). For example,
@@ -364,15 +364,15 @@ <h3><a href="#toc-entry-8">Tags set globally can be removed using <code>-tag</co
 deprecated (<a href="https://github.com/robotframework/robotframework/issues/4365">#4365</a>) and using the new <code>-tag</code> syntax is recommended. With
 keywords there was no similar functionality earlier.</p>
 <a name="dynamic-and-hybrid-library-apis-support-asynchronous-execution"></a>
-<h3><a href="#toc-entry-9">Dynamic and hybrid library APIs support asynchronous execution</a></h3>
+<h3><a href="#id121">Dynamic and hybrid library APIs support asynchronous execution</a></h3>
 <p>Dynamic and hybrid libraries nowadays support asynchronous execution.
 In practice the special methods like <code>get_keyword_names</code> and <code>run_keyword</code>
 can be implemented as async methods (<a href="https://github.com/robotframework/robotframework/issues/4803">#4803</a>).</p>
 <p>Async support was added to the normal static library API in Robot Framework
 6.1 (<a href="https://github.com/robotframework/robotframework/issues/4089">#4089</a>). A bug related to handling asynchronous keywords if execution
 is stopped gracefully has also been fixed (<a href="https://github.com/robotframework/robotframework/issues/4808">#4808</a>).</p>
 <a name="timestamps-in-result-model-and-output-xml-use-standard-format"></a>
-<h3><a href="#toc-entry-10">Timestamps in result model and output.xml use standard format</a></h3>
+<h3><a href="#id122">Timestamps in result model and output.xml use standard format</a></h3>
 <p>Timestamps used in the result model and stored to the output.xml file used custom
 format like <code>20231107 19:57:01.123</code> earlier. Non-standard formats are seldom
 a good idea, and in this case parsing the custom format turned out to be slow
@@ -663,7 +663,7 @@ <h3><a href="#toc-entry-23">Deprecated attributes in parsing, running and result
 <code>name</code>, <code>owner</code> and <code>source_name</code> instead.</li>
 </ul>
 <a name="other-deprecated-features"></a>
-<h3><a href="#toc-entry-24">Other deprecated features</a></h3>
+<h3><a href="#id136">Other deprecated features</a></h3>
 <ul>
 <li>Using embedded arguments with a variable that has a value not matching custom
 embedded argument patterns nowadays causes a deprecation warning (<a href="https://github.com/robotframework/robotframework/issues/4524">#4524</a>).
@@ -1300,4 +1300,4 @@ <h2><a href="#toc-entry-26">Full list of fixes and enhancements</a></h2>
 </tr>
 </tbody>
 </table>
-<p>Altogether 88 issues. View on the <a href="https://github.com/robotframework/robotframework/issues?q=milestone%3Av7.0">issue tracker</a>.</p>
+<p>Altogether 88 issues. View on the <a href="https://github.com/robotframework/robotframework/issues?q=milestone%3Av7.0">issue tracker</a>.</p>

test/markups/README.rst.html

@@ -10,7 +10,7 @@ <h2>Subtitle</h2>
 </div>
 <a name="header-2"></a>
 <a name="label-for-header-2"></a>
-<h2><a href="#toc-entry-1">Header 2</a></h2>
+<h2><a href="#id1">Header 2</a></h2>
 <ol>
 <li>Blah blah <code>code</code> blah</li>
 <li>More <code>code</code>, hooray</li>
@@ -109,7 +109,7 @@ <h2><a href="#toc-entry-1">Header 2</a></h2>
 </a>
 <img alt="Coverity Scan Build Status" src="https://scan.coverity.com/projects/621/badge.svg">
 <a name="field-list"></a>
-<h2><a href="#toc-entry-2">Field list</a></h2>
+<h2><a href="#id2">Field list</a></h2>
 <table frame="void" rules="none">