💎♻️：trans-repo tech transfer (gem-in-the-wip)

(※ OpenINF CQ Checks now to be re-impl'd here as well)

Pull Request Purpose

Make a selection on the purpose(s) of your changes.

This PR contains the following:

[ ] 🐞🔧 bugfixing (🐜/🦟/🐛/🦗/🐝 et al.)
[ ] 🆕🎏 implementation of new feature(s)
[ ] ♻️ refactoring(s)
[ ] 📄 documentation modification(s)
[ ] 🔮 other

Testing

Have you included any tests in your submission?

[ ] yes (bugfixes and features will not be merged without tests)
[ ] no

Breaking Changes

Have you modified any aspect public API surface (i.e., caused breakage)?

[ ] yes (breaking changes will not be merged unless necessary)
[ ] no

Description

A concise recap summarily detailing what all are the changes being made.

List of any relevant issue numbers:

Best Practices

The guides help you with the specifics of creating plugins. We also have some recommended best practices to help structure your plugin.

We recommend using a gem for your plugin. This will help you manage dependencies, keep separation from your site source code and allow you to share functionality across multiple projects.

— https://jekyllrb.com/docs/plugins/your-first-plugin/#best-practices

@DerekNonGeneric, suggest following best practice of literal in-house gem creation (version, release, etc.)

will be able to have desired ruby linting from RoR project over in separate repo

_Originally posted by @openinfbot in https://github.com/OpenINF/openinf.github.io/pull/1131#discussion_r1502630984_

OpenINF / openinf-jekyll-asset-path-plugin