Fix Popper documentation consistency

[ncovercash]

There are several props available to the Popper component which were not documented in the README.

Additionally, the placements auto-start and auto-end were missing from the AVAILABLE_PLACEMENTS array, despite being valid (looks like I missed these in #2004, whoops).

[github-actions]

Jest Unit Test Statistics

0 tests  ±0   0 ✔️ ±0   0s ⏱️ ±0s
0 suites ±0   0 💤 ±0 
0 files   ±0   0 ❌ ±0 

Results for commit 52e8432. ± Comparison against base commit cafbd45.

♻️ This comment has been updated with latest results.

[github-actions]

BigTest Unit Test Statistics

       1 files  ±0         1 suites  ±0   11s ⏱️ ±0s
1 416 tests ±0  1 395 ✔️ ±0  21 💤 ±0  0 ❌ ±0 
1 419 runs  ±0  1 398 ✔️ ±0  21 💤 ±0  0 ❌ ±0 

Results for commit 52e8432. ± Comparison against base commit cafbd45.

♻️ This comment has been updated with latest results.

[zburke]

Consider creating a Jira for this PR so we have way to document which release contains the auto-start and auto-end props.

[JohnC-80]

Things might get interesting for this component when we look at migrating to floating-ui and its possibilities for placement... Will potentially mean even more docs changes, so if we want to hold on this, will be okay...

[ncovercash]

@JohnC-80 IMO we should go ahead and merge this — the "new" placements are already accepted per the readme and supported by the code, just forgotten in the prop-types, so we're not adding something new

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarCloud