AO3-6862 Use official example domain

[SekoiaTree]

Pull Request Checklist

• Have you read "How to write the perfect pull request"?
• Have you read the contributing guidelines?
• Have you added tests for any changed functionality?
• Have you added the Jira issue number
  as the first thing in your pull request title (e.g. AO3-1234 Fix thing)
• Do you have fewer than 5 pull requests already open? If not, please wait
  until they are reviewed and merged before creating new pull requests.

Issue

https://otwarchive.atlassian.net/browse/AO3-6862

Purpose

Minor help document change: replace a "fake" domain with the official IANA example domain (and use https)

I also did a quick search for other incorrect example URLs. I didn't find any public ones, though I did find

otwarchive/spec/controllers/api/v2/api_works_spec.rb

Lines 21 to 25 in 6a471a1

	archivist: archivist.login,
	works: [
	{ external_author_name: "bar",
	external_author_email: "[email protected]",
	chapter_urls: ["http://foo"] }

but since that's just a test, probably fine. Also, a good amount of http (not s) links, but those mostly get redirected to HTTPS by modern browsers anyhow.

https://github.com/otwcode/otwarchive/blob/6a471a1447cedbed74c9090c5d0f11669a599914/features/fixtures/external_works.yml

also references external domains, but since the point of the test is to make sure that external imports work...

Testing Instructions

Look at the help page at https://test.archiveofourown.org/help/skins-creating.html (replace with localhost as appropriate) and see that it now uses example.com.

References

Not that I know of.

Credit

Sekoia, she/her. Jira account uses the same name.

[brianjaustin]

Hi, Sekoia, and thank you for the PR!

Everything looks good to me, so I've approved it. Once this is added to the next release, we'll merge the PR and send the changes through QA.

I've assigned the Jira issue to you and set its status to In Review so no one will mistakenly create a duplicate pull request. I've also given your account permission to comment on, assign, and transition issues in the future.

Thanks again for contributing! If you have any questions, you can contact us at [email protected].