directly embed ace and pikaday

this will allow them to be embedded in the binary created by `go install`

Author: cooper

LICENSE

@@ -1,4 +1,4 @@
-Copyright (c) 2020, Mitchell Cooper
+Copyright (c) 2024, Mitchell Cooper
 
 Permission to use, copy, modify, and/or distribute this software for any
 purpose with or without fee is hereby granted, provided that the above

NOTICE

@@ -0,0 +1,40 @@
+NOTICE
+
+This project includes third-party libraries and code. We acknowledge and thank the authors of these projects for their contributions.
+
+1. Ace Editor
+   https://github.com/ajaxorg/ace
+   License: "New" BSD 3-clause
+   Copyright (c) 2010, Ajax.org B.V.
+
+2. Pikaday
+   https://github.com/Pikaday/Pikaday
+   License: BSD & MIT
+   Copyright (c) 2014 David Bushell
+
+3. MooTools
+   https://mootools.net
+   License: MIT
+   Copyright (c) 2006-2014 Valerio Proietti
+
+4. tmpl.min.js
+   https://github.com/blueimp/JavaScript-Templates
+   License: MIT
+   Copyright (c) 2011 Sebastian Tschan, https://blueimp.net
+
+5. diff2html
+   https://github.com/rtfpessoa/diff2html
+   License: MIT
+   Copyright 2014-2016 Rodrigo Fernandes https://rtfpessoa.github.io/
+
+6. Font Awesome
+   https://github.com/FortAwesome/Font-Awesome
+   License: https://fontawesome.com/license/free
+        (Icons: CC BY 4.0, Fonts: SIL OFL 1.1, Code: MIT License)
+   Copyright (c) 2024 Fonticons, Inc.
+
+7. Color Picker
+   License: MIT
+   Copyright (c) 2007 John Dyer (http://johndyer.name)
+
+For full license texts, please refer to the LICENSE files in the respective repositories.

resources/adminifier/static/ext/ace/.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,11 @@
+<!--
+Most of the files here are generated with a build script, so You probably
+should submit your pull request to https://github.com/ajaxorg/ace instead
+-->
+
+*Issue #, if available:*
+
+*Description of changes:*
+
+
+By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

resources/adminifier/static/ext/ace/.github/workflows/publish.yml

@@ -0,0 +1,34 @@
+# This workflow will do a clean install of node dependencies, build the source code and run tests across different versions of node
+# For more information see: https://help.github.com/actions/language-and-framework-guides/using-nodejs-with-github-actions
+
+name: Publish to NPM
+on:
+  push:
+    tags:
+      - v*
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+    - uses: actions/checkout@v2
+    # Setup .npmrc file to publish to npm
+    - uses: actions/setup-node@v1
+      with:
+        node-version: '12.x'
+        registry-url: 'https://registry.npmjs.org'
+    - run: node -p "json=require('./package.json');if (json.dependencies || json.devDependencies) throw new Error()"
+    - run: node -p "window={}; require('./src-noconflict/ace.js').config.all"
+    - run: | 
+        # echo testing themes
+        for dir in src*; do 
+            for theme in $dir/theme-*; do 
+                node -e 'window = global;require("./'$dir'/ace.js");
+                var theme = require("'./$theme'");
+                if (!theme.cssClass || !theme.cssText) {
+                    throw new Error("Broken theme ./'$theme'")
+                } '
+            done
+        done
+    - run: npm publish
+      env:
+        NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}

resources/adminifier/static/ext/ace/.nojekyll

@@ -0,0 +1 @@
+disable jekyll on gh-pages

resources/adminifier/static/ext/ace/.npmignore

@@ -0,0 +1,3 @@
+demo/
+kitchen-sink.html
+* *

resources/adminifier/static/ext/ace/CHANGELOG.md

@@ -0,0 +1,4 @@
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+[email protected] with any additional questions or comments.

resources/adminifier/static/ext/ace/CODE_OF_CONDUCT.md

@@ -0,0 +1,61 @@
+# Contributing Guidelines
+
+Thank you for your interest in contributing to our project. Whether it's a bug report, new feature, correction, or additional 
+documentation, we greatly value feedback and contributions from our community.
+
+Please read through this document before submitting any issues or pull requests to ensure we have all the necessary 
+information to effectively respond to your bug report or contribution.
+
+
+## Reporting Bugs/Feature Requests
+
+We welcome you to use the GitHub issue tracker to report bugs or suggest features.
+
+When filing an issue, please check [existing open](https://github.com/ajaxorg/ace-builds/issues), or [recently closed](https://github.com/ajaxorg/ace-builds/issues?utf8=%E2%9C%93&q=is%3Aissue%20is%3Aclosed%20), issues to make sure somebody else hasn't already 
+reported the issue. Please try to include as much information as you can. Details like these are incredibly useful:
+
+* A reproducible test case or series of steps
+* The version of our code being used
+* Any modifications you've made relevant to the bug
+* Anything unusual about your environment or deployment
+
+
+## Contributing via Pull Requests
+Contributions via pull requests are much appreciated. Before sending us a pull request, please ensure that:
+
+1. You are working against the latest source on the *master* branch.
+2. You check existing open, and recently merged, pull requests to make sure someone else hasn't addressed the problem already.
+3. You open an issue to discuss any significant work - we would hate for your time to be wasted.
+
+To send us a pull request, please:
+
+1. Fork the repository.
+2. Modify the source; please focus on the specific change you are contributing. If you also reformat all the code, it will be hard for us to focus on your change.
+3. Ensure local tests pass.
+4. Commit to your fork using clear commit messages.
+5. Send us a pull request, answering any default questions in the pull request interface.
+6. Pay attention to any automated CI failures reported in the pull request, and stay involved in the conversation.
+
+GitHub provides additional document on [forking a repository](https://help.github.com/articles/fork-a-repo/) and 
+[creating a pull request](https://help.github.com/articles/creating-a-pull-request/).
+
+
+## Finding contributions to work on
+Looking at the existing issues is a great way to find something to contribute on. As our projects, by default, use the default GitHub issue labels ((enhancement/bug/duplicate/help wanted/invalid/question/wontfix), looking at any ['help wanted'](https://github.com/ajaxorg/ace-builds/labels/help%20wanted) issues is a great place to start. 
+
+
+## Code of Conduct
+This project has adopted the [Amazon Open Source Code of Conduct](https://aws.github.io/code-of-conduct). 
+For more information see the [Code of Conduct FAQ](https://aws.github.io/code-of-conduct-faq) or contact 
+[email protected] with any additional questions or comments.
+
+
+## Security issue notifications
+If you discover a potential security issue in this project we ask that you notify AWS/Amazon Security via our [vulnerability reporting page](http://aws.amazon.com/security/vulnerability-reporting/). Please do **not** create a public github issue.
+
+
+## Licensing
+
+See the [LICENSE](https://github.com/ajaxorg/ace-builds/blob/master/LICENSE) file for our project's licensing. We will ask you to confirm the licensing of your contribution.
+
+We may ask you to sign a [Contributor License Agreement (CLA)](http://en.wikipedia.org/wiki/Contributor_License_Agreement) for larger changes.