fix: update packaging image urls throughout

Author: lwasser

_posts/2022-11-21-what-makes-a-python-package-healthy.md

@@ -72,7 +72,7 @@ ecosystem. These packages tend to have smaller user bases, and smaller maintaine
 teams (or often are maintained by one volunteer person).
 
 <figure>
-    <a href="/images/python-packages/python-ecosystem-jake-vanderploss-pycon-2017.png"><img src="/images/python-packages/python-ecosystem-jake-vanderploss-pycon-2017.png" alt="Image used by Jake Vanderploss in the 2017 pycon conference that shows
+    <a href="/images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png"><img src="/images/python-packaging/python-ecosystem-jake-vanderploss-pycon-2017.png" alt="Image used by Jake Vanderploss in the 2017 pycon conference that shows
     the ecosystem of scientific python packages starting with foundational packages
     and moving out to the wealth of smaller, domain specific packages."></a>
     <figcaption>Image used by Jake Vanderploss in the 2017 pycon conference that shows

_posts/2023-03-22-demystifying-python-packaging.md

@@ -58,8 +58,8 @@ At the same time I noticed that many did not want to talk about
 Python packaging. And I wondered, why?
 
 <figure>
-    <a href="/images/python-packages/lion-meme-pyopensci.jpeg">
-    <img src="/images/python-packages/lion-meme-pyopensci.jpeg" style="max-width:100%" alt="A meme showing a mountain lion with it's little paw up like an italian mobster. the meme text says - so you want to talk about python packaging..">
+    <a href="/images/python-packaging/lion-meme-pyopensci.jpeg">
+    <img src="/images/python-packaging/lion-meme-pyopensci.jpeg" style="max-width:100%" alt="A meme showing a mountain lion with it's little paw up like an italian mobster. the meme text says - so you want to talk about python packaging..">
     </a>
     <figcaption>People didn't want to talk about Python packaging. It was such a painful, sore topic.
     </figcaption>
@@ -143,8 +143,8 @@ In general, users want to use the simplest approach to publish their packages on
 Remember - early wins go a long way.
 
 <figure>
-    <a href="/images/python-packages/dont-talk-about-peps-pyopensci.jpeg">
-    <img src="/images/python-packages/dont-talk-about-peps-pyopensci.jpeg" style="max-width:100%" alt="A meme from the movie flight flub showing brad pitt with his arms crossed in a black tshirt. The text says - the first rul of peps is do not talk about peps.">
+    <a href="/images/python-packaging/dont-talk-about-peps-pyopensci.jpeg">
+    <img src="/images/python-packaging/dont-talk-about-peps-pyopensci.jpeg" style="max-width:100%" alt="A meme from the movie flight flub showing brad pitt with his arms crossed in a black tshirt. The text says - the first rul of peps is do not talk about peps.">
     </a>
     <figcaption>At one point, I was trying to link to Python standards - known as PEPS (Python Enhancement Protocols) given everyone was sharing the various PEPs that tools follow. I was then told that we should avoid linking to these pages as they weren't intended for public consumption. If that is the case then how does the public get current information about standards? While I understood the goal, My mind was a bit blown. This was one of many points of confusion that I had to sort through.  :)
     </figcaption>

_posts/2023-06-14-pycon-maintainers-summit-python-packaging-talk-leah-wasser.md

@@ -76,8 +76,8 @@ I spent a bit of time in that video talking about how we create our guides.
 - Our process is normally several steps including an initial writing of content that is reviewed by experts. Followed by 2 rounds of open reviews of the content. The image below describes that process.
 
 <figure>
-    <a href="/images/python-packages/pycon-packaging-review-process.png">
-    <img src="/images/python-packages/pycon-packaging-review-process.png" style="max-width:100%" alt="Graphic that has a large purple thick arrow. The title says Python Packaging Guide - Our Process. The sections in the arrow include Talk with core experts (write a section of the guide), semi-closed review (core experts review), Open Review 1 (ping tool developers and maintainers and welcome broad community feedback) and Open Review 2 (welcome broad community feedback).">
+    <a href="/images/python-packaging/pycon-packaging-review-process.png">
+    <img src="/images/python-packaging/pycon-packaging-review-process.png" style="max-width:100%" alt="Graphic that has a large purple thick arrow. The title says Python Packaging Guide - Our Process. The sections in the arrow include Talk with core experts (write a section of the guide), semi-closed review (core experts review), Open Review 1 (ping tool developers and maintainers and welcome broad community feedback) and Open Review 2 (welcome broad community feedback).">
     </a>
     <figcaption>Image from my talk that shows our packaging guide review process. Our packaging guide is community-driven. This means that every page of the guide has been reviewed by dozens of people with expertise in the packaging space. While this meant that it is taking extra time to create the guide, it also means the community supports it. We value community knowledge and input at pyOpenSci.
     </figcaption>
@@ -91,8 +91,8 @@ packaging tools.
 _Leave no stone unturned_ (my motto when doing most things).
 
 <figure>
-    <a href="/images/python-packages/pyOS-package-guide-contributors.png">
-    <img src="/images/python-packages/pyOS-package-guide-contributors.png" style="max-width:100%" alt=".sdf">
+    <a href="/images/python-packaging/pyOS-package-guide-contributors.png">
+    <img src="/images/python-packaging/pyOS-package-guide-contributors.png" style="max-width:100%" alt=".sdf">
     </a>
     <figcaption>Image from my talk that shows our packaging guide review process. Our packaging guide is community-driven. This means that every page of the guide has been reviewed by dozens of people with expertise in the packaging space. While this meant that it is taking extra time to create the guide, it also means the community supports it. We value community knowledge and input at pyOpenSci.
     </figcaption>

_posts/2024-05-14-pyos-guide-to-pyconus-2024.md

@@ -52,8 +52,8 @@ Diversity and inclusion is core to the pyOpenSci mission, and we can't wait for
 *Hall C*\
 **[Leah Wasser](https://github.com/lwasser)**
 <figure>
-    <a href="/images/python-packages/lion-meme-pyopensci.jpeg">
-    <img src="/images/python-packages/lion-meme-pyopensci.jpeg" style="max-width:100%" alt="A puma leaning against a rock and flexing a front arm. Overlaid on the photo in meme text is the phrase 'so you want to talk about Python packaging.'">
+    <a href="/images/python-packaging/lion-meme-pyopensci.jpeg">
+    <img src="/images/python-packaging/lion-meme-pyopensci.jpeg" style="max-width:100%" alt="A puma leaning against a rock and flexing a front arm. Overlaid on the photo in meme text is the phrase 'so you want to talk about Python packaging.'">
     </a>
 </figure>
 We couldn't talk about PyCon US without talking about our Executive Director and Founder, Leah Wasser, who will be talking all things Python packaging! Python packaging can be a scary and confusing endeavor. The ecosystem can be thorny and filled with many decisions around which tool or approach to use. You’re also likely to get pricked by an approach or tutorial that doesn't work as expected. However, the packaging journey doesn’t have to be prickly - particularly for pure Python packages. By building community consensus around user goals and moderating healthy discussion, pyOpenSci is paving a smooth, thorn-free path for successful packaging.